Re: [PATCH v10 00/35] kmemcg shrinkers

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thu, 6 Jun 2013 11:37:03 +0400 Glauber Costa <glommer@xxxxxxxxxxxxx> wrote:

> On 06/06/2013 11:18 AM, Andrew Morton wrote:
> > The shrinker stuff seems sensible and straightforward and I expect we
> > can proceed with that at the normal pace.  The memcg changes struck me
> > as being hairy as hell and I'd really like to see the other memcg
> > people go through it carefully.
> > 
> > Of course, "new series" doesn't give you an easily accessible tree to
> > target.  I could drop it all again to give you a clean shot at
> > tomorrow's -next?
> If you just keep them on top (not really sure how hard it is for you), I
> can just remove them all and apply a new series on top.

I could do that but then anyone else who wants to test the code has to
do the same thing.  Dropping them out of -next does seem the clean
approach.

We still need to work out what to do with
memcg-debugging-facility-to-access-dangling-memcgs.patch btw.  See
other email.
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux Ext4 Filesystem]     [Union Filesystem]     [Filesystem Testing]     [Ceph Users]     [Ecryptfs]     [AutoFS]     [Kernel Newbies]     [Share Photos]     [Security]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux Cachefs]     [Reiser Filesystem]     [Linux RAID]     [Samba]     [Device Mapper]     [CEPH Development]
  Powered by Linux