All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Vernet <void@manifault.com>
To: dthaler1968=40googlemail.com@dmarc.ietf.org
Cc: bpf@vger.kernel.org, bpf@ietf.org
Subject: Re: [Bpf] Follow up on "call helper function by address" terminology
Date: Fri, 5 Apr 2024 16:50:44 -0500	[thread overview]
Message-ID: <20240405215044.GC19691@maniforge> (raw)
In-Reply-To: <0a0f01da8795$5496b250$fdc416f0$@gmail.com>

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

On Fri, Apr 05, 2024 at 01:10:38PM -0700, dthaler1968=40googlemail.com@dmarc.ietf.org wrote:
> At IETF 119, we agreed that "by address" should be changed to
> something else in the ISA.  The term "legacy ID" was used during the
> discussion but Christoph (if I remember right) pointed out that such
> IDs are not deprecated per se.  Hence "legacy" may not be the right
> word since we use that word with legacy packet access instructions
> that are deprecated. We decided to take further discussion to the
> list, hence this email.
> 
> We need some term to distinguish them from BTF IDs, so another
> alternative might be "non-BTF ID".

Non-BTF ID is fine with me. Any objections?

Thanks,
David

[-- 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: dthaler1968=40googlemail.com@dmarc.ietf.org
Cc: bpf@vger.kernel.org, bpf@ietf.org
Subject: Re: [Bpf] Follow up on "call helper function by address" terminology
Date: Fri, 5 Apr 2024 16:50:44 -0500	[thread overview]
Message-ID: <20240405215044.GC19691@maniforge> (raw)
Message-ID: <20240405215044.IF3cjY7FVDcscH2KM-fUrJ0HaFvquyFCrfjSgTe93W4@z> (raw)
In-Reply-To: <0a0f01da8795$5496b250$fdc416f0$@gmail.com>


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

On Fri, Apr 05, 2024 at 01:10:38PM -0700, dthaler1968=40googlemail.com@dmarc.ietf.org wrote:
> At IETF 119, we agreed that "by address" should be changed to
> something else in the ISA.  The term "legacy ID" was used during the
> discussion but Christoph (if I remember right) pointed out that such
> IDs are not deprecated per se.  Hence "legacy" may not be the right
> word since we use that word with legacy packet access instructions
> that are deprecated. We decided to take further discussion to the
> list, hence this email.
> 
> We need some term to distinguish them from BTF IDs, so another
> alternative might be "non-BTF ID".

Non-BTF ID is fine with me. Any objections?

Thanks,
David

[-- 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

  reply	other threads:[~2024-04-05 21:50 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 20:10 Follow up on "call helper function by address" terminology dthaler1968
2024-04-05 20:10 ` [Bpf] " dthaler1968=40googlemail.com
2024-04-05 21:50 ` David Vernet [this message]
2024-04-05 21:50   ` David Vernet
2024-04-07  6:57   ` Watson Ladd
2024-04-07  6:57     ` Watson Ladd
2024-04-07 16:23     ` dthaler1968
2024-04-07 16:23       ` dthaler1968=40googlemail.com
2024-04-18  7:01       ` Christoph Hellwig
2024-04-18 12:46         ` dthaler1968
2024-04-18 12:46           ` dthaler1968=40googlemail.com

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=20240405215044.GC19691@maniforge \
    --to=void@manifault.com \
    --cc=bpf@ietf.org \
    --cc=bpf@vger.kernel.org \
    --cc=dthaler1968=40googlemail.com@dmarc.ietf.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 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.