linux-numa.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Petr Holasek <pholasek@redhat.com>
Cc: Cliff Wickman <cpw@sgi.com>, linux-numa@vger.kernel.org
Subject: Re: [PATCH] numactl: new --allphyscpubind/-A option
Date: Thu, 5 Sep 2013 18:45:11 +0200	[thread overview]
Message-ID: <20130905164511.GQ19750@two.firstfloor.org> (raw)
In-Reply-To: <1378390451-25639-1-git-send-email-pholasek@redhat.com>

On Thu, Sep 05, 2013 at 04:14:11PM +0200, Petr Holasek wrote:
> This patch adds new --allphyscpubind/-A option to set cpu bind to all possible
> physical CPUs, not only to ones from the current cpuset as --physcpubind does
> now.
> 
> We have discussed this topic about year ago here:
> 
> http://thread.gmane.org/gmane.linux.kernel.numa/798

Patch looks good to me.

-Andi

  reply	other threads:[~2013-09-05 16:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-05 14:14 [PATCH] numactl: new --allphyscpubind/-A option Petr Holasek
2013-09-05 16:45 ` Andi Kleen [this message]
2013-09-05 19:54   ` Andi Kleen

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=20130905164511.GQ19750@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=cpw@sgi.com \
    --cc=linux-numa@vger.kernel.org \
    --cc=pholasek@redhat.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;
as well as URLs for NNTP newsgroup(s).