From: Peter Zijlstra <peterz@infradead.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E . McKenney" <paulmck@kernel.org>,
Boqun Feng <boqun.feng@gmail.com>,
"H . Peter Anvin" <hpa@zytor.com>, Paul Turner <pjt@google.com>,
linux-api@vger.kernel.org,
Christian Brauner <christian.brauner@ubuntu.com>,
David.Laight@ACULAB.COM, carlos@redhat.com,
Peter Oskolkov <posk@posk.io>
Subject: Re: [RFC PATCH 1/2] rseq: extend struct rseq with numa node id
Date: Tue, 1 Feb 2022 12:08:52 +0100 [thread overview]
Message-ID: <20220201110852.GW20638@worktop.programming.kicks-ass.net> (raw)
In-Reply-To: <8735l3k3hu.fsf@mid.deneb.enyo.de>
On Mon, Jan 31, 2022 at 10:19:09PM +0100, Florian Weimer wrote:
> It can be used to implement getcpu purely in userspace, too. I had
> plan to hack this together with a node ID cache in TLS, which should
> offer pretty much the same functionality (except for weird CPU
> topology changes which alter the node ID of a previously used CPU).
PowerPC does that quite a lot..
next prev parent reply other threads:[~2022-02-01 11:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 20:55 [RFC PATCH 1/2] rseq: extend struct rseq with numa node id Mathieu Desnoyers
2022-01-31 20:55 ` [RFC PATCH 2/2] selftests/rseq: Implement rseq numa node id field selftest Mathieu Desnoyers
2022-01-31 21:19 ` [RFC PATCH 1/2] rseq: extend struct rseq with numa node id Florian Weimer
2022-01-31 21:26 ` Mathieu Desnoyers
2022-02-01 11:08 ` Peter Zijlstra [this message]
2022-02-01 12:11 ` Florian Weimer
2022-01-31 21:22 ` Mathieu Desnoyers
2022-02-01 11:08 ` Peter Zijlstra
2022-02-01 12:07 ` Florian Weimer
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=20220201110852.GW20638@worktop.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=David.Laight@ACULAB.COM \
--cc=boqun.feng@gmail.com \
--cc=carlos@redhat.com \
--cc=christian.brauner@ubuntu.com \
--cc=fw@deneb.enyo.de \
--cc=hpa@zytor.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=paulmck@kernel.org \
--cc=pjt@google.com \
--cc=posk@posk.io \
--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 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.