The I/O drives down the free pages enough probably.
You can't spinlock around the kmalloc either. The kmalloc may cause I/O
requests to be queued to enable kmalloc to complete..
> I actually only need it in 136 byte chunks, the only place I got 8k from was
> that's
> about how much had been allocated total when kmalloc started failing. But I
> think it's probably due to reading/writing from it during allocation.
Allocating over a page size significantly increases the change of failure
because its guaranteed physically linear - so will cause swapping
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/