On Fri, Jul 22, 2005 at 08:23:19PM -0300, Márcio Oliveira wrote: <snip> > > > Roger, thanks for the information. > > I'm using Update 4 kernels (2.4.21-27.ELsmp - This kernel have some > mm / oom fixes) and don't have big problems when create large files, > plus the server is a 32-bit machine. > > Neil said that the problem can be Low Memory and I think it too. > > I read the following message on the list: > > http://marc.theaimsgroup.com/?l=linux-kernel&m=112044530919567&w=4 > > The problem seems like a I/O issue. Can I/O (like storage devices) > consume a large amount of low memory? Neil also said that the kernel is > trying to move lots of data to the disk and it's a module might require > such large memory. Somebody know how can I identify what is using Low > Memory on my system? > The best way I can think to do that is take a look at /proc/slabinfo. That will likely give you a pointer to which area of code is eating up your memory.
> The older questions in the message are: > > The server has 16GB RAM and 16GB swap. When the OOM kill conditions > happens, the system has ~6GB RAM used, ~10GB RAM cached and 16GB free swap. > Is that indicate that the server can't allocate Low Memory and starts OOM > conditions? Because the High Memory is OK, right? > Based on the sysrq-m info you posted it looks like due to fragmentation the largest chunk of memory you can allocate is 2MB (perhaps less depending on address space availability). If you can build a test kernel to do a show_state rather than a show_mem at the beginning of oom_kil, then you should be able to tell who is trying to do an allocation that leads to kswapd calling out_of_memory. > Thanks to all! > > Regards, > Márcio > > -- /*************************************************** *Neil Horman *Software Engineer *Red Hat, Inc. [EMAIL PROTECTED] *gpg keyid: 1024D / 0x92A74FA1 *http://pgp.mit.edu ***************************************************/ - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/