From: Dave Thaler <dthaler1968@googlemail.com> To: bpf@vger.kernel.org Cc: bpf@ietf.org, Dave Thaler <dthaler1968@gmail.com> Subject: [PATCH bpf-next] bpf, docs: Clarify which legacy packet instructions existed Date: Tue, 30 Jan 2024 19:37:59 -0800 [thread overview] Message-ID: <20240131033759.3634-1-dthaler1968@gmail.com> (raw) As discussed in mailing list discussion at https://mailarchive.ietf.org/arch/msg/bpf/5LnnKm093cGpOmDI9TnLQLBXyys/ this patch updates the "Legacy BPF Packet access instructions" section to clarify which instructions are deprecated (vs which were never defined and so are not deprecated). Signed-off-by: Dave Thaler <dthaler1968@gmail.com> --- Documentation/bpf/standardization/instruction-set.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/bpf/standardization/instruction-set.rst b/Documentation/bpf/standardization/instruction-set.rst index af43227b6..cf08337bf 100644 --- a/Documentation/bpf/standardization/instruction-set.rst +++ b/Documentation/bpf/standardization/instruction-set.rst @@ -635,7 +635,9 @@ Legacy BPF Packet access instructions ------------------------------------- BPF previously introduced special instructions for access to packet data that were -carried over from classic BPF. However, these instructions are +carried over from classic BPF. These instructions used an instruction +class of BPF_LD, a size modifier of BPF_W, BPF_H, or BPF_B, and a +mode modifier of BPF_ABS or BPF_IND. However, these instructions are deprecated and should no longer be used. All legacy packet access instructions belong to the "legacy" conformance group instead of the "basic" conformance group. -- 2.40.1
WARNING: multiple messages have this Message-ID (diff)
From: Dave Thaler <dthaler1968=40googlemail.com@dmarc.ietf.org> To: bpf@vger.kernel.org Cc: bpf@ietf.org, Dave Thaler <dthaler1968@gmail.com> Subject: [Bpf] [PATCH bpf-next] bpf, docs: Clarify which legacy packet instructions existed Date: Tue, 30 Jan 2024 19:37:59 -0800 [thread overview] Message-ID: <20240131033759.3634-1-dthaler1968@gmail.com> (raw) Message-ID: <20240131033759.XV9tV3t88WWtPPefXc-pxAH6DPsSce0T6fplYx-DoO0@z> (raw) As discussed in mailing list discussion at https://mailarchive.ietf.org/arch/msg/bpf/5LnnKm093cGpOmDI9TnLQLBXyys/ this patch updates the "Legacy BPF Packet access instructions" section to clarify which instructions are deprecated (vs which were never defined and so are not deprecated). Signed-off-by: Dave Thaler <dthaler1968@gmail.com> --- Documentation/bpf/standardization/instruction-set.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Documentation/bpf/standardization/instruction-set.rst b/Documentation/bpf/standardization/instruction-set.rst index af43227b6..cf08337bf 100644 --- a/Documentation/bpf/standardization/instruction-set.rst +++ b/Documentation/bpf/standardization/instruction-set.rst @@ -635,7 +635,9 @@ Legacy BPF Packet access instructions ------------------------------------- BPF previously introduced special instructions for access to packet data that were -carried over from classic BPF. However, these instructions are +carried over from classic BPF. These instructions used an instruction +class of BPF_LD, a size modifier of BPF_W, BPF_H, or BPF_B, and a +mode modifier of BPF_ABS or BPF_IND. However, these instructions are deprecated and should no longer be used. All legacy packet access instructions belong to the "legacy" conformance group instead of the "basic" conformance group. -- 2.40.1 -- Bpf mailing list Bpf@ietf.org https://www.ietf.org/mailman/listinfo/bpf
next reply other threads:[~2024-01-31 3:38 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-31 3:37 Dave Thaler [this message] 2024-01-31 3:37 ` [Bpf] [PATCH bpf-next] bpf, docs: Clarify which legacy packet instructions existed Dave Thaler 2024-01-31 18:44 ` Yonghong Song 2024-01-31 18:44 ` [Bpf] " Yonghong Song 2024-01-31 19:02 ` David Vernet 2024-01-31 19:02 ` [Bpf] " David Vernet 2024-02-01 10:40 ` patchwork-bot+netdevbpf
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=20240131033759.3634-1-dthaler1968@gmail.com \ --to=dthaler1968@googlemail.com \ --cc=bpf@ietf.org \ --cc=bpf@vger.kernel.org \ --cc=dthaler1968@gmail.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: linkBe 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).