From: Peter Zijlstra <peterz@infradead.org>
To: Florian Weimer <fweimer@redhat.com>
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>
Subject: Re: [PATCH v4] sched/core: Use zero length to reset cpumasks in sched_setaffinity()
Date: Wed, 4 Oct 2023 15:52:36 +0200 [thread overview]
Message-ID: <20231004135236.GB19999@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <871qeaefco.fsf@oldenburg.str.redhat.com>
On Wed, Oct 04, 2023 at 02:34:15PM +0200, Florian Weimer wrote:
> * Peter Zijlstra:
>
> > Subject: sched: Add CPU_FILL()
> >
> > Add the CPU_FILL() macros to easily create an all-set cpumask.
> >
> > FreeBSD also provides this macro with this semantic.
> >
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
>
> My main concer is that obtaining the size of the mask, or at least an
> approximiation is not exactly easy. If there's an expectation that
> applications reset the mask more often than they do today (I don't have
> the full context here), then we'd some decent interface to get the
> approriate size.
Isn't sysconf(_SC_NPROCESSORS_CONF) the right number ?
next prev parent reply other threads:[~2023-10-04 13:52 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
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 [this message]
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=20231004135236.GB19999@noisy.programming.kicks-ass.net \
--to=peterz@infradead.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=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 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).