Pekka Enberg put forth on 8/23/2010 4:37 AM: > On 8/23/10 1:40 AM, Christoph Lameter wrote: >> On Sun, 22 Aug 2010, Pekka Enberg wrote: >> >>> In Stan's case, it's a order-1 GFP_ATOMIC allocation but there are >>> only order-0 pages available. Mel, any recent page allocator fixes in >>> 2.6.35 or 2.6.36-rc1 that Stan/Mikael should test? >> This is the TCP slab? Best fix would be in the page allocator. However, >> in this particular case the slub allocator would be able to fall back to >> an order 0 allocation and still satisfy the request. >> > Looking at the stack trace of the oops, I think Stan has CONFIG_SLAB > which doesn't have order-0 fallback. That is correct. The menuconfig help screen led me to believe the SLAB allocator was the "safe" choice: "CONFIG_SLAB: The regular slab allocator that is established and known to work well in all environments" Should I be using SLUB instead? Any downsides to SLUB on an old and slow (500 MHz) single core dual CPU box with <512MB RAM? Also, what is the impact of these oopses? Despite the entries in dmesg, the system "seems" to be running ok. Or is this simply the calm before the impending storm? -- Stan -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxxx For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>