linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shirley Ma <mashirle@us.ibm.com>
To: linux-kernel@vger.kernel.org, mingo@redhat.com, peterz@infradead.org
Cc: netdev@vger.kernel.org, "Michael S. Tsirkin" <mst@redhat.com>,
	vivek@us.ibm.com, sri@us.ibm.com, sri@us.ibm.com
Subject: Re: [RFC PATCH 0/1] sched: Add a new API to find the prefer idlest cpu
Date: Fri, 17 Aug 2012 08:39:46 -0700	[thread overview]
Message-ID: <1345217986.16533.1.camel@oc3660625478.ibm.com> (raw)
In-Reply-To: <1343026634.13461.15.camel@oc3660625478.ibm.com>

Hello Ingo, Peter,

	Have you had chance to review below patch?

Thanks
Shirley

On Sun, 2012-07-22 at 23:57 -0700, Shirley Ma wrote:
> Introduce a new API to choose per-cpu thread from cgroup control cpuset
> (allowed) and preferred cpuset (local numa-node).
> 
> The receiving cpus of a networking device are not under cgroup controls.
> When such a networking device uses per-cpu thread model, the cpu which
> is chose to process the packets might not be part of cgroup cpusets
> without this API. On numa system, the preferred cpusets would help to
> reduce expensive cross memory access to/from the other node.
> 
> Signed-off-by: Shirley Ma <xma@us.ibm.com>
> ---
> 
>  include/linux/sched.h |    2 ++
>  kernel/sched/fair.c   |   30 ++++++++++++++++++++++++++++++
>  2 files changed, 32 insertions(+), 0 deletions(-)
> 
> Thanks
> Shirley
> 
> 
> 
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 



  parent reply	other threads:[~2012-08-17 15:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-23  6:57 [RFC PATCH 0/1] sched: Add a new API to find the prefer idlest cpu Shirley Ma
2012-07-23  6:59 ` [RFC PATCH 1/1] " Shirley Ma
2012-08-17 15:39 ` Shirley Ma [this message]
2012-08-17 16:48   ` [RFC PATCH 0/1] " Peter Zijlstra
2012-08-17 16:58     ` Shirley Ma

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=1345217986.16533.1.camel@oc3660625478.ibm.com \
    --to=mashirle@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=mst@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=sri@us.ibm.com \
    --cc=vivek@us.ibm.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).