> After simple bash fork bombing (about 200 forks) on my UP Celeron/96MB
> I get quite a lot %u-allocations failed, but only when swap is turned
> I'm not familiar with LinuxVM.. so... is it normal behaviour ? or (if not)
> what's happening when such messages are printed my kernel ?
This is perfectly normal behaviour:
1) on your system, you have no process limit configured for
yourself so you can start processes until all resources
(memory, file descriptors, ...) are used
2) when all processes are used, there really is no way the
kernel can buy you more hardware on ebay and install it
on the fly ... all it can do is start failing allocations
On production systems, good admins setup per-user limits for
the various resources so no single user is able to run the
system into the ground.
-- DMCA, SSSCA, W3C? Who cares? http://thefreeworld.net/ (volunteers needed)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/