From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Waiman Long <longman@redhat.com>, Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
linux-kernel@vger.kernel.org, Phil Auld <pauld@redhat.com>,
Brent Rowsell <browsell@redhat.com>,
Peter Hunt <pehunt@redhat.com>,
Florian Weimer <fweimer@redhat.com>
Subject: Re: [PATCH v4] sched/core: Use zero length to reset cpumasks in sched_setaffinity()
Date: Wed, 4 Oct 2023 12:06:29 +0200 [thread overview]
Message-ID: <ZR05JXPgOXb4kuHl@gmail.com> (raw)
In-Reply-To: <20231004094330.GL1539@noisy.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
> On Wed, Oct 04, 2023 at 11:23:41AM +0200, Ingo Molnar wrote:
>
> > > if (user_mask) {
> > > - cpumask_copy(user_mask, in_mask);
> > > + /*
> > > + * All-set user cpumask resets affinity and drops the explicit
> > > + * user mask.
> > > + */
> > > + cpumask_and(user_mask, in_mask, cpu_possible_mask);
> > > + if (cpumask_equal(user_mask, cpu_possible_mask)) {
> > > + kfree(user_mask);
> > > + user_mask = NULL;
> > > + }
> >
> > Question: is there any observable behavioral difference between current
> > (old) all-set cpumask calls and the patched (new) one?
>
> Very little I think -- the main difference is that we no longer carry
> the ->user_cpus_ptr mask around, and that saves a little masking.
So calling with a full mask would actually work fine on 'old' kernels too,
as it's a 'reset' event in essence. (With a bit of allocation & masking
overhead.)
This pretty unambiguously marks the full-mask solution as the superior ABI ...
Thanks,
Ingo
next prev parent reply other threads:[~2023-10-04 10:06 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-03 20:57 [PATCH v4] sched/core: Use zero length to reset cpumasks in sched_setaffinity() Waiman Long
2023-10-04 8:36 ` Peter Zijlstra
2023-10-04 9:23 ` Ingo Molnar
2023-10-04 9:43 ` Peter Zijlstra
2023-10-04 10:06 ` Ingo Molnar [this message]
2023-10-04 12:19 ` Waiman Long
2023-10-04 12:34 ` Florian Weimer
2023-10-04 12:41 ` Waiman Long
2023-10-04 12:55 ` Florian Weimer
2023-10-04 16:23 ` Waiman Long
2023-10-04 13:52 ` Peter Zijlstra
2023-10-04 13:54 ` Peter Zijlstra
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=ZR05JXPgOXb4kuHl@gmail.com \
--to=mingo@kernel.org \
--cc=bristot@redhat.com \
--cc=browsell@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=fweimer@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=pehunt@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.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.