> On Fri, 5 Oct 2001, Krzysztof Rusocki wrote:
> > 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
> > off.
> > 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
So it needs a handbrake in case of a emergency? The box at work deadlocks
or crashes. I can hardly call that normal operational behaviour.
I have a Dell PE 2500 (Serverworks LE) with 2GB ram and 2 1.13Ghz
processors. If I disable HIGHMEM (4GB) support the box does not produce
these allocations messages and does not deadlock or die under the same
load or worse. What I used was a mongo.pl with 5 processes (does not
matter if the
fs is ext2 reiserfs or xfs) and the box dies within minutes/seconds after
starting the benchmark.
This happens using either 2.4.10-xfs or 2.4.11-pre3-xfs.
Using a single process hides the issue.
> 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.
The system is beafy enough to tolerate something mundane as this. It
should definitely not die.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to firstname.lastname@example.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/