From: Miao Xie <miaox@cn.fujitsu.com>
To: Paul Menage <menage@google.com>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>, Paul Jackson <pj@usa.net>,
Andrew Morton <akpm@linux-foundation.org>,
mingo@elte.hu, linux-kernel@vger.kernel.org,
cl@linux-foundation.org, Derek Fults <dfults@sgi.com>
Subject: Re: [PATCH] cpuset: fix allocating page cache/slab object on the unallowed node when memory spread is set
Date: Thu, 12 Feb 2009 13:57:24 +0800 [thread overview]
Message-ID: <4993BA44.2070809@cn.fujitsu.com> (raw)
In-Reply-To: <6599ad830902111719n2750ac29u458face30bf3f7cb@mail.gmail.com>
on 2009-2-12 9:19 Paul Menage wrote:
> On Wed, Feb 11, 2009 at 4:54 PM, Nick Piggin <nickpiggin@yahoo.com.au> wrote:
>> It would be possible, depending on timing, for the allocating thread to
>> see either pre or post mems_allowed even if access was fully locked.
>
> Right - seeing either the pre set or the post set is fine.
>
>> The only difference is that a partially changed mems_allowed could be
>> seen. But what does this really mean? Some combination of the new and
>> the old nodes. I don't think this is too much of a problem.
>
> But if the old and new nodes are disjoint, that could lead to seeing no nodes.
>
> Also, having the results of cpuset_zone_allowed() and
> cpuset_current_mems_allowed change at random times over the course of
> a call to alloc_pages() might cause interesting effects (e.g. we make
> progress freeing pages from one set of nodes, and then call
> get_page_from_freelist() on a different set of nodes).
>
>> This could work if we *really* need an atomic snapshot of mems_allowed.
>> seqcount synchronisation would be an alternative too that could allow
>> sleeping more easily than SRCU (OTOH if you don't need sleeping, then
>> RCU should be faster than seqcount).
>>
>> But I'm not convinced we do need this to be atomic.
>
> It's possible that I'm being overly-paranoid here. The decision to
> make mems_allowed updates be purely pulled by the task itself predates
> my involvement with cpusets code by a long time. Paul Jackson (CC'd)
> may have opinions here, but I suspect his sgi.com email address no
> longer works, and I don't have any more recent address for him.
I think it's pj@usa.net(CC'd).
Author: Paul Jackson <pj@sgi.com>
Date: Fri Oct 3 15:23:42 2008 -0700
cpusets: remove pj from cpuset maintainers
Remove myself from the kernel MAINTAINERS file for cpusets. I am leaving
SGI and probably will not be active in Linux kernel work. I can be
reached at <pj@usa.net>. Contact Derek Fults <dfults@sgi.com> for future
SGI+cpuset related issues. I'm off to the next chapter of this good life.
Signed-off-by: Paul Jackson <pj@sgi.com>
Cc: Paul Menage <menage@google.com>
Cc: Derek Fults <dfults@sgi.com>
Cc: John Hesterberg <jh@sgi.com>
Cc: Paul Jackson <pj@usa.net>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Thanks!
Miao
>
> Paul
>
>
>
next prev parent reply other threads:[~2009-02-12 6:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-21 8:06 [PATCH] cpuset: fix allocating page cache/slab object on the unallowed node when memory spread is set Miao Xie
2009-01-21 8:30 ` Nick Piggin
2009-01-21 10:41 ` Paul Menage
2009-02-03 3:05 ` Miao Xie
2009-01-27 22:42 ` Andrew Morton
2009-01-28 16:38 ` Christoph Lameter
2009-02-03 3:25 ` Miao Xie
2009-02-03 22:16 ` Andrew Morton
2009-02-03 22:49 ` Paul Menage
2009-02-04 9:31 ` Miao Xie
2009-02-06 19:19 ` Paul Menage
2009-02-09 4:02 ` Nick Piggin
2009-02-10 11:37 ` Paul Menage
2009-02-12 0:54 ` Nick Piggin
2009-02-12 1:19 ` Paul Menage
2009-02-12 1:55 ` Nick Piggin
2009-02-12 1:58 ` Paul Menage
2009-02-12 8:23 ` Miao Xie
2009-02-12 21:53 ` Paul Menage
2009-02-12 8:27 ` Miao Xie
2009-02-12 10:40 ` Nick Piggin
2009-02-12 5:57 ` Miao Xie [this message]
2009-02-12 11:06 ` Paul Jackson
2009-02-04 9:03 ` Miao Xie
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=4993BA44.2070809@cn.fujitsu.com \
--to=miaox@cn.fujitsu.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux-foundation.org \
--cc=dfults@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=menage@google.com \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=pj@usa.net \
/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