> What this routine does is call vmalloc() repeatedly for a number of 1MB
> chunks until it fails or until it's allocated 128MB (CLEAR_BLOCK_COUNT
> is equal to 128 in this case). Then, it starts freeing them.
>
> The side-effect of this routine is to page-out up to 128MB of RAM.
> Unfortunately, on a 128MB machine, the 118th call to vmalloc() hangs the
> system. I was expecting it to return NULL instead.
>
> Is this a bug in vmalloc()? If so, is there a work-around that I can use?
vmalloc shouldnt be hanging the box, although in 2.4.2 the out of memory
handling is not too reliable. You have to understand vmalloc isnt meant to
be used that way and the kernel gets priority over user space for allocs so
is able to get itself to the point it killed off all user space.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Aug 31 2001 - 21:00:35 EST