From: 王贇 <yun.wang@linux.alibaba.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
"open list:SCHEDULER" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] why can't dynamic isolation just like the static way
Date: Wed, 12 Feb 2020 09:35:18 +0800 [thread overview]
Message-ID: <6b4fda32-b9b0-b8ce-968e-7e5a65a7e1f0@linux.alibaba.com> (raw)
In-Reply-To: <20200211090028.4e12d02e@gandalf.local.home>
On 2020/2/11 下午10:00, Steven Rostedt wrote:
> On Tue, 11 Feb 2020 12:43:50 +0100
> Peter Zijlstra <peterz@infradead.org> wrote:
>
>> On Tue, Feb 11, 2020 at 04:17:34PM +0800, 王贇 wrote:
>>> Hi, folks
>>>
>>> We are dealing with isolcpus these days and try to do the isolation
>>> dynamically.
>>>
>>> The kernel doc lead us into the cpuset.sched_load_balance, it's fine
>>> to achieve the dynamic isolation with it, however we got problem with
>>> the systemd stuff.
>>
>> Then don't use systemd :-) Also, if systemd is the problem, why are you
>> bugging us?
>
> [ Background. Peter is someone that doesn't even use systemd. ;-) ]
I would be happy to get rid of that too ;-) but seems like it's getting
popular now as the basic init stuff, and I guess they have no idea about
how they are breaking the dynamic isolation.
Regards,
Michael Wang
>
> -- Steve
>
next prev parent reply other threads:[~2020-02-12 1:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 8:17 王贇
2020-02-11 11:43 ` Peter Zijlstra
2020-02-11 14:00 ` Steven Rostedt
2020-02-12 1:35 ` 王贇 [this message]
2020-02-12 1:30 ` 王贇
2020-02-11 13:54 ` Steven Rostedt
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=6b4fda32-b9b0-b8ce-968e-7e5a65a7e1f0@linux.alibaba.com \
--to=yun.wang@linux.alibaba.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
/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®