From: "Li,Rongqing" <lirongqing@baidu.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: "peterz@infradead.org" <peterz@infradead.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"mingo@kernel.org" <mingo@kernel.org>,
"srikar@linux.vnet.ibm.com" <srikar@linux.vnet.ibm.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"wanpengli@tencent.com" <wanpengli@tencent.com>
Subject: 答复: [PATCH] sched/isolation: allow isolcpus and nohz_full for different cpus
Date: Tue, 21 Apr 2020 01:35:41 +0000 [thread overview]
Message-ID: <1d04cd31871648128267dda5303db99e@baidu.com> (raw)
In-Reply-To: <20200420163409.GB10024@lenoir>
> -----邮件原件-----
> 发件人: Frederic Weisbecker [mailto:frederic@kernel.org]
> 发送时间: 2020年4月21日 0:34
> 收件人: Li,Rongqing <lirongqing@baidu.com>
> 抄送: peterz@infradead.org; tglx@linutronix.de; mingo@kernel.org;
> srikar@linux.vnet.ibm.com; linux-kernel@vger.kernel.org
> 主题: Re: [PATCH] sched/isolation: allow isolcpus and nohz_full for different
> cpus
>
> On Thu, Apr 16, 2020 at 04:51:18PM +0800, Li RongQing wrote:
> > when both isolcpus and nohz_full are set, their cpus must be same now,
> > in fact isolcpus and nohz_full are not related, and different cpus are
> > expected for some cases, for example, some cores for polling threads
> > wants to isolcpus, and some cores for dedicated threads, only
> > nohz_full is expected
> >
> > so define two housekeeping mask to save these two configuration
> > separately and make cpus same only when both nohz_full and isolcpus
> > with nohz are passed into kernel
> >
> > fix a build error when CONFIG_CPUMASK_OFFSTACK is not configured
> > reported by kbuild test robot <lkp@intel.com>
>
> What is the usecase when you want to affine managed interrupt?
> Do you only want to affine IRQ or do you also want to affine every unbound
> work, such as kthread, workqueues, timers, etc...?
>
As cloud compute node, both qemu and ovs-dpdk run on it
Some cores are bound to run ovs-dpdk, and should be isolated from any disturb (isolcpus= nohz_full= rcu_nocbs= )
Other cores run kvm qemu, and do not wants to be disturbed by hrtimer (only nohz_full=) by using this feature https://patchwork.kernel.org/cover/11033533/
Thanks
-LiRongQing
> In the end I would like to group the isolation features that only make sense
> together. So we could end up with three cpumasks, one for "domains", one for
> "nohz" and one for all "unbound" works.
>
> In fact "domains" should even disappear and become "unbound" +
> "load_balance", as that's the desired outcome of having NULL domains.
>
> I'm trying to prepare a suitable interface for all that in cpusets where we
> already have the load_balance part.
>
> Thanks.
prev parent reply other threads:[~2020-04-21 2:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-16 8:51 [PATCH] sched/isolation: allow isolcpus and nohz_full for different cpus Li RongQing
2020-04-20 16:34 ` Frederic Weisbecker
2020-04-21 1:35 ` Li,Rongqing [this message]
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=1d04cd31871648128267dda5303db99e@baidu.com \
--to=lirongqing@baidu.com \
--cc=frederic@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=tglx@linutronix.de \
--cc=wanpengli@tencent.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).