Re: memcg: slab control

[KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>]

On Thu, 26 Nov 2009 12:10:52 +0300
Pavel Emelyanov <xemul@parallels.com> wrote:

> >> Anyway, I agree that we need another
> >> slabcg, Pavel did some work in that area and posted patches, but they
> >> were mostly based and limited to SLUB (IIRC).
> 
> I'm ready to resurrect the patches and port them for slab.
> But before doing it we should answer one question.
> 
> Consider we have two kmalloc-s in a kernel code - one is
> user-space triggerable and the other one is not. From my
> POV we should account for the former one, but should not
> for the latter.
> 
> If so - how should we patch the kernel to achieve that goal?
> 
> > My point is that most of the kernel codes cannot work well when kmalloc(small area)
> > returns NULL.
> 
> :) That's not so actually. As our experience shows kernel lives fine
> when kmalloc returns NULL (this doesn't include drivers though).
> 
One issue it comes to my mind is that file system can return -EIO because
kmalloc() returns NULL. the kernel may work fine but terrible to users ;)


Thanks,
-Kame

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>