From: Marcelo Tosatti <mtosatti@redhat.com>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Chris Friesen <chris.friesen@windriver.com>,
linux-kernel@vger.kernel.org, Christoph Lameter <cl@linux.com>,
Vu Tran <vu.tran@windriver.com>,
Jim Somerville <Jim.Somerville@windriver.com>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH] affine kernel threads to specified cpumask
Date: Tue, 24 Mar 2020 08:38:29 -0300 [thread overview]
Message-ID: <20200324113829.GA16502@fuller.cnet> (raw)
In-Reply-To: <87imiuq0cg.fsf@nanos.tec.linutronix.de>
On Mon, Mar 23, 2020 at 09:31:59PM +0100, Thomas Gleixner wrote:
> Chris,
>
> Chris Friesen <chris.friesen@windriver.com> writes:
> > On 3/23/2020 10:22 AM, Thomas Gleixner wrote:
> >> Marcelo Tosatti <mtosatti@redhat.com> writes:
> >>> This allows CPU isolation (that is not allowing certain threads
> >>> to execute on certain CPUs) without using the isolcpus= parameter,
> >>> making it possible to enable load balancing on such CPUs
> >>> during runtime.
> >>
> >> I'm surely missing some background information, but that sentence does
> >> not make any sense to me.
> >
> > The idea is to affine general kernel threads to specific "housekeeping"
> > CPUs, while still allowing load balancing of tasks.
> >
> > The isolcpus= boot parameter would prevent kernel threads from running
> > on the isolated CPUs, but it disables load balancing on the isolated CPUs.
>
> So why can't we just have a isolcpus mode which allows that instead of
> adding more command line options which are slightly different?
>
> We just added some magic for managed interrupts to isolcpus, which is
> surely interesting for your scenario as well...
>
> Thanks,
>
> tglx
Hi Thomas, Chris,
Works for me, will adjust and resend.
next prev parent reply other threads:[~2020-03-24 11:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-23 13:54 [PATCH] affine kernel threads to specified cpumask Marcelo Tosatti
2020-03-23 15:29 ` Chris Friesen
2020-03-24 15:07 ` Marcelo Tosatti
2020-03-23 16:22 ` Thomas Gleixner
2020-03-23 17:02 ` Chris Friesen
2020-03-23 20:31 ` Thomas Gleixner
2020-03-24 11:38 ` Marcelo Tosatti [this message]
2020-03-24 15:20 ` [PATCH v2] isolcpus: " Marcelo Tosatti
2020-03-24 15:56 ` Chris Friesen
2020-03-24 16:50 ` Marcelo Tosatti
2020-03-25 0:30 ` Frederic Weisbecker
2020-03-25 11:47 ` Marcelo Tosatti
2020-03-26 16:20 ` Frederic Weisbecker
2020-03-26 16:52 ` Frederic Weisbecker
2020-03-27 12:07 ` Marcelo Tosatti
2020-03-25 18:05 ` David Laight
2020-03-26 11:28 ` Marcelo Tosatti
2020-03-26 16:22 ` Frederic Weisbecker
2020-03-26 16:32 ` Chris Friesen
2020-03-26 16:51 ` Frederic Weisbecker
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=20200324113829.GA16502@fuller.cnet \
--to=mtosatti@redhat.com \
--cc=Jim.Somerville@windriver.com \
--cc=akpm@linux-foundation.org \
--cc=chris.friesen@windriver.com \
--cc=cl@linux.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=vu.tran@windriver.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.