BPF List
 help / color / mirror / Atom feed
From: David Vernet <void@manifault.com>
To: Dave Thaler <dthaler1968=40googlemail.com@dmarc.ietf.org>
Cc: bpf@vger.kernel.org, bpf@ietf.org, Dave Thaler <dthaler1968@gmail.com>
Subject: Re: [Bpf] [PATCH bpf-next] bpf, docs: Add introduction for use in the ISA Internet Draft
Date: Mon, 22 Apr 2024 14:38:47 -0500	[thread overview]
Message-ID: <20240422193847.GB18561@maniforge> (raw)
In-Reply-To: <20240422190942.24658-1-dthaler1968@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1659 bytes --]

On Mon, Apr 22, 2024 at 12:09:42PM -0700, Dave Thaler wrote:
> The proposed intro paragraph text is derived from the first paragraph
> of the IETF BPF WG charter at https://datatracker.ietf.org/wg/bpf/about/
> 
> Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
> ---
>  Documentation/bpf/standardization/instruction-set.rst | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/bpf/standardization/instruction-set.rst b/Documentation/bpf/standardization/instruction-set.rst
> index d03d90afb..b44bdacd0 100644
> --- a/Documentation/bpf/standardization/instruction-set.rst
> +++ b/Documentation/bpf/standardization/instruction-set.rst
> @@ -5,7 +5,11 @@
>  BPF Instruction Set Architecture (ISA)
>  ======================================
>  
> -This document specifies the BPF instruction set architecture (ISA).
> +eBPF (which is no longer an acronym for anything), also commonly
> +referred to as BPF, is a technology with origins in the Linux kernel
> +that can run untrusted programs in a privileged context such as an

Perhaps this should be phrased as:

...that can run untrusted programs in privileged contexts such as the
operating system kernel.

Not sure if that's actually a grammar correction but it sounds more
correct in my head. Wdyt?

Regardless:

Acked-by: David Vernet <void@manifault.com>

> +operating system kernel. This document specifies the BPF instruction
> +set architecture (ISA).
>  
>  Documentation conventions
>  =========================
> -- 
> 2.40.1
> 
> -- 
> Bpf mailing list
> Bpf@ietf.org
> https://www.ietf.org/mailman/listinfo/bpf

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: David Vernet <void@manifault.com>
To: Dave Thaler <dthaler1968=40googlemail.com@dmarc.ietf.org>
Cc: bpf@vger.kernel.org, bpf@ietf.org, Dave Thaler <dthaler1968@gmail.com>
Subject: Re: [Bpf] [PATCH bpf-next] bpf, docs: Add introduction for use in the ISA Internet Draft
Date: Mon, 22 Apr 2024 14:38:47 -0500	[thread overview]
Message-ID: <20240422193847.GB18561@maniforge> (raw)
Message-ID: <20240422193847.uekANs-OYl0igjKfX1hVPVzS7ucTFt4IiHiTgGkzdOw@z> (raw)
In-Reply-To: <20240422190942.24658-1-dthaler1968@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1659 bytes --]

On Mon, Apr 22, 2024 at 12:09:42PM -0700, Dave Thaler wrote:
> The proposed intro paragraph text is derived from the first paragraph
> of the IETF BPF WG charter at https://datatracker.ietf.org/wg/bpf/about/
> 
> Signed-off-by: Dave Thaler <dthaler1968@gmail.com>
> ---
>  Documentation/bpf/standardization/instruction-set.rst | 6 +++++-
>  1 file changed, 5 insertions(+), 1 deletion(-)
> 
> diff --git a/Documentation/bpf/standardization/instruction-set.rst b/Documentation/bpf/standardization/instruction-set.rst
> index d03d90afb..b44bdacd0 100644
> --- a/Documentation/bpf/standardization/instruction-set.rst
> +++ b/Documentation/bpf/standardization/instruction-set.rst
> @@ -5,7 +5,11 @@
>  BPF Instruction Set Architecture (ISA)
>  ======================================
>  
> -This document specifies the BPF instruction set architecture (ISA).
> +eBPF (which is no longer an acronym for anything), also commonly
> +referred to as BPF, is a technology with origins in the Linux kernel
> +that can run untrusted programs in a privileged context such as an

Perhaps this should be phrased as:

...that can run untrusted programs in privileged contexts such as the
operating system kernel.

Not sure if that's actually a grammar correction but it sounds more
correct in my head. Wdyt?

Regardless:

Acked-by: David Vernet <void@manifault.com>

> +operating system kernel. This document specifies the BPF instruction
> +set architecture (ISA).
>  
>  Documentation conventions
>  =========================
> -- 
> 2.40.1
> 
> -- 
> Bpf mailing list
> Bpf@ietf.org
> https://www.ietf.org/mailman/listinfo/bpf

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

[-- Attachment #2: Type: text/plain, Size: 76 bytes --]

-- 
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf

  parent reply	other threads:[~2024-04-22 19:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-22 19:09 [PATCH bpf-next] bpf, docs: Add introduction for use in the ISA Internet Draft Dave Thaler
2024-04-22 19:09 ` [Bpf] " Dave Thaler
2024-04-22 19:38 ` David Vernet [this message]
2024-04-22 19:38   ` David Vernet
2024-04-22 20:18   ` dthaler1968
2024-04-22 20:18     ` dthaler1968=40googlemail.com
2024-04-23 20:11     ` David Vernet
2024-04-23 20:11       ` David Vernet
2024-04-26  2:20 ` 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=20240422193847.GB18561@maniforge \
    --to=void@manifault.com \
    --cc=bpf@ietf.org \
    --cc=bpf@vger.kernel.org \
    --cc=dthaler1968=40googlemail.com@dmarc.ietf.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: 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