From: Christoph Hellwig <hch@lst.de>
To: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Cc: Christoph Hellwig <hch@lst.de>, Jonathan Corbet <corbet@lwn.net>,
Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>,
Andrii Nakryiko <andrii@kernel.org>,
Martin KaFai Lau <kafai@fb.com>, Song Liu <songliubraving@fb.com>,
Yonghong Song <yhs@fb.com>,
John Fastabend <john.fastabend@gmail.com>,
KP Singh <kpsingh@kernel.org>,
"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>,
Network Development <netdev@vger.kernel.org>,
bpf <bpf@vger.kernel.org>
Subject: Re: [PATCH 3/5] bpf, docs: Better document the legacy packet access instruction
Date: Thu, 3 Feb 2022 18:40:10 +0100 [thread overview]
Message-ID: <20220203174010.GA16681@lst.de> (raw)
In-Reply-To: <CAADnVQLiEQFzON5OEV_LVYzqJuZ68e0AnqhNC++vptbed6ioEw@mail.gmail.com>
On Thu, Feb 03, 2022 at 09:32:38AM -0800, Alexei Starovoitov wrote:
> These two places make it sound like it's interpreter only behavior.
> I've reworded it like:
> -the interpreter context is a pointer to networking packet. ``BPF_ABS``
> +the program context is a pointer to networking packet. ``BPF_ABS``
>
> -interpreter will abort the execution of the program.
> +program execution will be aborted.
>
> and pushed to bpf-next with the rest of patches.
The interpreter thing is actually unchanged from the old text, but I
totally agree with your fixup. Thanks!
next prev parent reply other threads:[~2022-02-03 17:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 18:36 event more eBPF instruction set documentation improvements Christoph Hellwig
2022-01-31 18:36 ` [PATCH 1/5] bpf, docs: Document the byte swapping instructions Christoph Hellwig
2022-02-03 17:40 ` patchwork-bot+netdevbpf
2022-01-31 18:36 ` [PATCH 2/5] bpf, docs: Better document the regular load and store instructions Christoph Hellwig
2022-01-31 18:36 ` [PATCH 3/5] bpf, docs: Better document the legacy packet access instruction Christoph Hellwig
2022-02-03 17:32 ` Alexei Starovoitov
2022-02-03 17:40 ` Christoph Hellwig [this message]
2022-02-03 17:44 ` Alexei Starovoitov
2022-01-31 18:36 ` [PATCH 4/5] bpf, docs: Better document the extended instruction format Christoph Hellwig
2022-01-31 18:36 ` [PATCH 5/5] bpf, docs: Better document the atomic instructions Christoph Hellwig
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=20220203174010.GA16681@lst.de \
--to=hch@lst.de \
--cc=alexei.starovoitov@gmail.com \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=corbet@lwn.net \
--cc=daniel@iogearbox.net \
--cc=john.fastabend@gmail.com \
--cc=kafai@fb.com \
--cc=kpsingh@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=yhs@fb.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.