mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Paul Menage" <menage@google.com>
To: "Paul Jackson" <pj@sgi.com>
Cc: "Andrew Morton" <akpm@osdl.org>,
	linux-kernel@vger.kernel.org,
	"Nick Piggin" <nickpiggin@yahoo.com.au>,
	"Andi Kleen" <ak@suse.de>, "Christoph Lameter" <clameter@sgi.com>
Subject: Re: [PATCH] cpuset - rework cpuset_zone_allowed api
Date: Fri, 8 Dec 2006 08:51:01 -0800	[thread overview]
Message-ID: <6599ad830612080851q55fe8c95m9f00a2a9a3779dc4@mail.gmail.com> (raw)
In-Reply-To: <20061208112152.12631.67436.sendpatchset@jackhammer.engr.sgi.com>

On 12/8/06, Paul Jackson <pj@sgi.com> wrote:
>
> -int __cpuset_zone_allowed(struct zone *z, gfp_t gfp_mask)
> +int __cpuset_zone_allowed_softwall(struct zone *z, gfp_t gfp_mask)
>  {
>         int node;                       /* node that zone z is on */
>         const struct cpuset *cs;        /* current cpuset ancestors */
> @@ -2335,6 +2351,40 @@ int __cpuset_zone_allowed(struct zone *z
>         return allowed;
>  }

While you're changing this, is there a good reason not to check
is_mem_exclusive() *before* taking callback_mutex and calling
nearest_exclusive_ancestor()?

something like:

rcu_read_lock();
exc = is_mem_exclusive(rcu_dereference(current->cs));
rcu_read_unlock();
if (exc)
  return 1;

... take callback_mutex, etc ...

Paul

  reply	other threads:[~2006-12-08 16:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 11:21 Paul Jackson
2006-12-08 16:51 ` Paul Menage [this message]
2006-12-09  0:28   ` Paul Jackson
2006-12-09  6:10 ` Andrew Morton

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=6599ad830612080851q55fe8c95m9f00a2a9a3779dc4@mail.gmail.com \
    --to=menage@google.com \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=clameter@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    --cc=pj@sgi.com \
    /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

all inboxes | Powered by JetHome®