[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <6599ad830803260821r5c5b56f3pd381659d0866c87b@mail.gmail.com>
Date: Wed, 26 Mar 2008 08:21:59 -0700
From: "Paul Menage" <menage@...gle.com>
To: balbir@...ux.vnet.ibm.com
Cc: linux-mm@...ck.org, "Hugh Dickins" <hugh@...itas.com>,
"Sudhir Kumar" <skumar@...ux.vnet.ibm.com>,
"YAMAMOTO Takashi" <yamamoto@...inux.co.jp>, lizf@...fujitsu.com,
linux-kernel@...r.kernel.org, taka@...inux.co.jp,
"David Rientjes" <rientjes@...gle.com>,
"Pavel Emelianov" <xemul@...nvz.org>,
"Andrew Morton" <akpm@...ux-foundation.org>,
"KAMEZAWA Hiroyuki" <kamezawa.hiroyu@...fujitsu.com>
Subject: Re: [RFC][-mm] Memory controller add mm->owner
On Wed, Mar 26, 2008 at 4:41 AM, Balbir Singh <balbir@...ux.vnet.ibm.com> wrote:
>
> Hmmm.. the 99.9% of the time is just guess work (not measured, could be possibly
> true). I see and understand your code below. But before I try and implement
> something like that, I was wondering why zap_threads() does not have that
> heuristic. That should explain my inhibition.
>
> Can anyone elaborate on zap_threads further?
>
zap_threads() has to find *all* the other users, whereas in this case
we only have to find one other user.
Paul
--
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