From: "Paul Menage" <menage@google.com>
To: balbir@linux.vnet.ibm.com
Cc: linux-mm@kvack.org, Hugh Dickins <hugh@veritas.com>,
Sudhir Kumar <skumar@linux.vnet.ibm.com>,
YAMAMOTO Takashi <yamamoto@valinux.co.jp>,
lizf@cn.fujitsu.com, linux-kernel@vger.kernel.org,
taka@valinux.co.jp, David Rientjes <rientjes@google.com>,
Pavel Emelianov <xemul@openvz.org>,
Andrew Morton <akpm@linux-foundation.org>,
KAMEZAWA Hiroyuki <kamezawa.hiroyu@jp.fujitsu.com>
Subject: Re: [RFC][-mm] Memory controller add mm->owner
Date: Wed, 26 Mar 2008 08:21:59 -0700 [thread overview]
Message-ID: <6599ad830803260821r5c5b56f3pd381659d0866c87b@mail.gmail.com> (raw)
In-Reply-To: <47EA3684.60107@linux.vnet.ibm.com>
On Wed, Mar 26, 2008 at 4:41 AM, Balbir Singh <balbir@linux.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, 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>
next prev parent reply other threads:[~2008-03-26 15:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-24 14:01 Balbir Singh
2008-03-24 15:03 ` Paul Menage
2008-03-24 16:21 ` Balbir Singh
2008-03-24 16:34 ` Paul Menage
2008-03-24 17:33 ` Balbir Singh
2008-03-24 17:46 ` Paul Menage
2008-03-25 11:41 ` Balbir Singh
2008-03-26 10:29 ` Balbir Singh
2008-03-26 11:20 ` Paul Menage
2008-03-26 11:41 ` Balbir Singh
2008-03-26 15:21 ` Paul Menage [this message]
2008-03-25 1:26 ` Li Zefan
2008-03-25 15:48 ` Balbir Singh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6599ad830803260821r5c5b56f3pd381659d0866c87b@mail.gmail.com \
--to=menage@google.com \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=hugh@veritas.com \
--cc=kamezawa.hiroyu@jp.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lizf@cn.fujitsu.com \
--cc=rientjes@google.com \
--cc=skumar@linux.vnet.ibm.com \
--cc=taka@valinux.co.jp \
--cc=xemul@openvz.org \
--cc=yamamoto@valinux.co.jp \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox