From: "Jose E. Marchesi" <jose.marchesi@oracle.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Barret Rhoden <brho@google.com>, Josh Don <joshdon@google.com>,
Hao Luo <haoluo@google.com>,
davemarchevsky@meta.com, Tejun Heo <tj@kernel.org>,
David Vernet <dvernet@meta.com>, Neel Natu <neelnatu@google.com>,
Jack Humphries <jhumphri@google.com>,
bpf@vger.kernel.org, ast@kernel.org
Subject: Re: BPF memory model
Date: Mon, 16 Oct 2023 19:17:54 +0200 [thread overview]
Message-ID: <87o7gyqyf1.fsf@oracle.com> (raw)
In-Reply-To: <5b23c67b-8b15-4d54-8f38-c201a6842b20@paulmck-laptop> (Paul E. McKenney's message of "Mon, 16 Oct 2023 09:48:21 -0700")
> On Tue, Sep 19, 2023 at 11:55:42AM -0400, Barret Rhoden wrote:
>> On 9/19/23 05:52, Paul E. McKenney wrote:
>> > Just to make sure that I understand, the idea is to compile from (say)
>> > __atomic_load_n() to BPF instructions, correct? Or is this compiling all
>> > the way to the target x86/ARMv8/whatever machine instructions?
>>
>> correct; i'm compiling with clang -target bpf to BPF instructions, which
>> should be spitting out the appropriate BPF atomic ops. then i hope that if
>> i get the compiler to emit the reads and writes in the correct order, that
>> the JIT maintains that order when it turns them into x86/whatever.
>
> Hopefully better late than never, here is a draft:
>
> https://docs.google.com/document/d/1TaSEfWfLnRUi5KqkavUQyL2tThJXYWHS15qcbxIsFb0/edit?usp=sharing
>
> Please do feel free to add relevant comments.
Nice :-)
/me reads carefully
next prev parent reply other threads:[~2023-10-16 17:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 22:00 BPF memory model Josh Don
2023-09-08 8:42 ` Paul E. McKenney
2023-09-08 20:26 ` Josh Don
2023-09-08 22:07 ` Tejun Heo
2023-09-08 23:16 ` Alexei Starovoitov
2023-09-09 12:47 ` Paul E. McKenney
2023-09-18 15:09 ` Barret Rhoden
2023-09-19 9:52 ` Paul E. McKenney
2023-09-19 15:55 ` Barret Rhoden
2023-10-16 16:48 ` Paul E. McKenney
2023-10-16 17:17 ` Jose E. Marchesi [this message]
2023-11-13 18:53 ` Barret Rhoden
2023-11-13 20:03 ` Paul E. McKenney
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=87o7gyqyf1.fsf@oracle.com \
--to=jose.marchesi@oracle.com \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=brho@google.com \
--cc=davemarchevsky@meta.com \
--cc=dvernet@meta.com \
--cc=haoluo@google.com \
--cc=jhumphri@google.com \
--cc=joshdon@google.com \
--cc=neelnatu@google.com \
--cc=paulmck@kernel.org \
--cc=tj@kernel.org \
/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