All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Paul Jackson <pj@sgi.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [2/3] {PREFIX:-x86_64}: Convert mempolicies to nodemask_t
Date: Mon, 12 Sep 2005 20:42:57 +0200	[thread overview]
Message-ID: <200509122042.57328.ak@suse.de> (raw)
In-Reply-To: <20050912022615.0140cc64.pj@sgi.com>

On Monday 12 September 2005 11:26, Paul Jackson wrote:
> Andi wrote:
> > Convert mempolicies to nodemask_t


Thanks for the review.


>  1) Can the include of 'linux/bitmap.h' be removed from the file
>     linux/include/linux/mempolicy.h?

Done.

>  2) /* AK: shouldn't this error out instead? */
I'll leave this to you.


>  3) Either this current patch of Andi's, or the patch considered for (2)
>     above should also convert whatever kernel/cpuset.c call the mempolicy.c
>     code is making from bitmaps to nodemasks, rather than convert to
> bitmaps across the boundary:
>
> 	cpuset_restrict_to_mems_allowed(nodes_addr(*nodes));
Leaving this to you too

(BTW I have one patch for cpusets pending to improve the fast path,
need to test it a little bit more before sending off though) 

>
>  4) Should the following line:
>
> 	+	PDprintk("setting mode %d nodes[0] %lx\n", mode, nodes_addr(nodes)[0]);
>
>     instead be:
>
> 	+	PDprintk("setting mode %d nodes[0] %lx\n", mode, nodes_addr(*nodes)[0]);
Fixed.

>
>   5) If anyone ever (even for debugging) adds something to the nodemask_t
Fixed.


>  6) How come I don't see changes for the 'compat_sys_get_mempolicy()'
> routine?

Because it doesn't work with nodemask_ts, but only with variable length
user buffers.

>
>  7) Do -not- add one for the next node in interleave_nodes():
Fixed (+ 8) 

Thanks,
-Andi

  parent reply	other threads:[~2005-09-12 18:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-10 11:58 [2/3] {PREFIX:-x86_64}: Convert mempolicies to nodemask_t Andi Kleen
2005-09-12  9:26 ` Paul Jackson
2005-09-12 11:35   ` Paul Jackson
2005-09-12 18:42   ` Andi Kleen [this message]
2005-09-12 19:39     ` Paul Jackson

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=200509122042.57328.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.