[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4F447904.90500@openvz.org>
Date: Wed, 22 Feb 2012 09:11:32 +0400
From: Konstantin Khlebnikov <khlebnikov@...nvz.org>
To: Andi Kleen <andi@...stfloor.org>
CC: "linux-mm@...ck.org" <linux-mm@...ck.org>,
Andrew Morton <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Hugh Dickins <hughd@...gle.com>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [PATCH v2 00/22] mm: lru_lock splitting
Andi Kleen wrote:
> Konstantin Khlebnikov<khlebnikov@...nvz.org> writes:
>
> Konstantin,
>
>> There complete patch-set with my lru_lock splitting
>> plus all related preparations and cleanups rebased to next-20120210
>
> On large systems we're also seeing lock contention on the lru_lock
> without using memcgs. Any thoughts how this could be extended for this
> situation too?
We can split lru_lock by pfn-based interleaving.
After all these cleanups it is very easy. I already have patch for this.
>
> Thanks,
>
> -Andi
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists