mm: critical shortage of bounce buffers
Hi list members,
I've recently encountered the following message on a machine running RedHat's 2.4.3-12 kernel :
"mm: critical shortage of bounce buffers"
I've searched through the kernel sources, but my 'find' just can't locate this string anywhere.
Why does this message appear (apparently during high network load with the intel eepro100 driver or e1000 driver). Is bounce buffers really in use on a x86 machine with 2GB of RAM (normal smp RedHat kernel, not enterprise)??
I appreciate any feedback.
Thanks,
Signature · 4 lines
Steffen Persvold | Scalable Linux Systems | Try out the world's best mailto:[email protected] | http://www.scali.com | performing MPI implementation: Tel: (+47) 2262 8950 | Olaf Helsets vei 6 | - ScaMPI 1.12.2 - Fax: (+47) 2262 8951 | N0621 Oslo, NORWAY | >300MBytes/s and <4uS latency
Quoted 7 lines
I've recently encountered the following message on a machine running RedHat's 2.4.3-12 kernel :
"mm: critical shortage of bounce buffers"
I've searched through the kernel sources, but my 'find' just can't locate this string anywhere.
Its in the high mem handling routines. It means the machine stalled for a moment doing I/O because it had no memory below 1Gb to use.
Quoted 3 lines
Why does this message appear (apparently during high network load with the intel eepro100 driver or e1000 driver). Is bounce buffers really in use on a x86 machine with 2GB of RAM (normal smp RedHat kernel, not enterprise)??
The answer is yes. You can actually build yourself a custom none bounce buffer 1.8GB kernel with about 2Gb of user virtual space per app. For some applications it will perform better.
Quoted 11 lines · Alan Cox
Quoted 8 lines
I've recently encountered the following message on a machine running RedHat's 2.4.3-12 kernel :
"mm: critical shortage of bounce buffers"
I've searched through the kernel sources, but my 'find' just can't locate this string anywhere.
Its in the high mem handling routines. It means the machine stalled for a moment doing I/O because it had no memory below 1Gb to use.
But why does it need to have memory below 1Gb ?? Normally, 32bit PCI DMA controllers (such as network cards and disk controllers) can access up to 4GB of physical memory within the machine, so unless you are using the CONFIG_HIGHMEM4G option it shouldn't need bounce buffers. Or am I missing something here (something like the second physical GB is actually in the address range 4GB->)???
Quoted 8 lines
Quoted 4 lines
Why does this message appear (apparently during high network load with the intel eepro100 driver or e1000 driver). Is bounce buffers really in use on a x86 machine with 2GB of RAM (normal smp RedHat kernel, not enterprise)??
The answer is yes. You can actually build yourself a custom none bounce buffer 1.8GB kernel with about 2Gb of user virtual space per app. For some applications it will perform better.
There's no CONFIG option for that right (like the old CONFIG_2GB option on 2.2 kernels) ? I'll have to manually go in and edit the header files in asm-i386. Would the 2.2 (e.g 2.2.19) kernel have the same problems with bounce buffers or is this not implemented on 2.2 ??
Regards,
Signature · 4 lines
Steffen Persvold | Scalable Linux Systems | Try out the world's best mailto:[email protected] | http://www.scali.com | performing MPI implementation: Tel: (+47) 2262 8950 | Olaf Helsets vei 6 | - ScaMPI 1.12.2 - Fax: (+47) 2262 8951 | N0621 Oslo, NORWAY | >300MBytes/s and <4uS latency
Quoted 11 lines · Steffen Persvold
Quoted 9 lines · Alan Cox
Quoted 8 lines
I've recently encountered the following message on a machine running RedHat's 2.4.3-12 kernel :
"mm: critical shortage of bounce buffers"
I've searched through the kernel sources, but my 'find' just can't locate this string anywhere.
Quoted 7 lines
Quoted 2 lines
Its in the high mem handling routines. It means the machine stalled for a moment doing I/O because it had no memory below 1Gb to use.
But why does it need to have memory below 1Gb ?? Normally, 32bit PCI DMA controllers (such as network cards and disk controllers) can access up to 4GB of physical memory within the machine, so unless you are using the
CONFIG_HIGHMEM4Goption it shouldn't need bounce buffers.
Sorry that should have been the CONFIG_HIGHMEM64G option. I think the CONFIG_HIGHMEM4G option could manage without bounce buffers.
Regards,
Signature · 4 lines
Steffen Persvold | Scalable Linux Systems | Try out the world's best mailto:[email protected] | http://www.scali.com | performing MPI implementation: Tel: (+47) 2262 8950 | Olaf Helsets vei 6 | - ScaMPI 1.12.2 - Fax: (+47) 2262 8951 | N0621 Oslo, NORWAY | >300MBytes/s and <4uS latency
Quoted 9 lines
Quoted 2 lines
Its in the high mem handling routines. It means the machine stalled for a moment doing I/O because it had no memory below 1Gb to use.
But why does it need to have memory below 1Gb ?? Normally, 32bit PCI DMA controllers (such as network cards and disk controllers) can access up to 4GB of physical memory within the machine, so unless you are using the
CONFIG_HIGHMEM4Goption it shouldn't need bounce buffers. Or am I missing something here (something like the second physical GB is actually in the address range 4GB->)???
The core code doesn't know if the device is PIO or DMA, and it cannot pass virtually unmapped objects to the block layer. This is what Jens has been fixing.