From: Marcelo Tosatti <mtosatti@redhat.com>
To: Frederic Weisbecker <frederic@kernel.org>
Cc: linux-kernel@vger.kernel.org, Christoph Lameter <cl@linux.com>,
Thomas Gleixner <tglx@linutronix.de>,
Juri Lelli <juri.lelli@redhat.com>, Nitesh Lal <nilal@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [patch 0/5] optionally sync per-CPU vmstats counter on return to userspace
Date: Tue, 6 Jul 2021 11:17:23 -0300 [thread overview]
Message-ID: <20210706141723.GA68914@fuller.cnet> (raw)
In-Reply-To: <20210706140920.GA68399@fuller.cnet>
On Tue, Jul 06, 2021 at 11:09:20AM -0300, Marcelo Tosatti wrote:
> > > And I suspect some other people won't like much a new extension
> > > to isolcpus.
> >
> > Why is that so?
>
> Ah, yes, that would be PeterZ.
>
> IIRC his main point was that its not runtime changeable.
> We can (partially fix that), if that is the case.
>
> Peter, was that the only problem you saw with isolcpus interface?
Oh, and BTW, isolcpus=managed_irq flag was recently added due to another
isolation bug.
This problem is the same category, so i don't see why it should be
treated especially (yes, i agree isolcpus= interface should be
improved, but thats what is available today).
next prev parent reply other threads:[~2021-07-06 14:34 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-01 21:03 [patch 0/5] optionally sync per-CPU vmstats counter on return to userspace Marcelo Tosatti
2021-07-01 21:03 ` [patch 1/5] sched: isolation: introduce vmstat_sync isolcpu flags Marcelo Tosatti
2021-07-01 21:03 ` [patch 2/5] common entry: add hook for isolation to __syscall_exit_to_user_mode_work Marcelo Tosatti
2021-07-01 21:03 ` [patch 3/5] mm: vmstat: optionally flush per-CPU vmstat counters on return to userspace Marcelo Tosatti
2021-07-01 23:11 ` kernel test robot
2021-07-02 6:50 ` kernel test robot
2021-07-01 21:03 ` [patch 4/5] mm: vmstat: move need_update Marcelo Tosatti
2021-07-01 21:03 ` [patch 5/5] mm: vmstat_refresh: avoid queueing work item if cpu stats are clean Marcelo Tosatti
2021-07-02 4:10 ` kernel test robot
2021-07-02 4:43 ` kernel test robot
2021-07-02 8:00 ` [patch 0/5] optionally sync per-CPU vmstats counter on return to userspace Christoph Lameter
2021-07-02 11:52 ` Marcelo Tosatti
2021-07-02 11:59 ` Marcelo Tosatti
2021-07-05 14:26 ` Christoph Lameter
2021-07-05 14:45 ` Marcelo Tosatti
2021-07-02 12:30 ` Frederic Weisbecker
2021-07-02 15:28 ` Marcelo Tosatti
2021-07-06 13:09 ` Frederic Weisbecker
2021-07-06 14:05 ` Marcelo Tosatti
2021-07-06 14:09 ` Marcelo Tosatti
2021-07-06 14:17 ` Marcelo Tosatti [this message]
2021-07-06 16:15 ` Peter Zijlstra
2021-07-06 16:53 ` Marcelo Tosatti
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=20210706141723.GA68914@fuller.cnet \
--to=mtosatti@redhat.com \
--cc=cl@linux.com \
--cc=frederic@kernel.org \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nilal@redhat.com \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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