BPF List
 help / color / mirror / Atom feed
From: dthaler1968@googlemail.com
To: <bpf@vger.kernel.org>, <bpf@ietf.org>
Subject: Follow up on "call helper function by address" terminology
Date: Fri, 5 Apr 2024 13:10:38 -0700	[thread overview]
Message-ID: <0a0f01da8795$5496b250$fdc416f0$@gmail.com> (raw)

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".

Thoughts, or other alternatives?

Dave


WARNING: multiple messages have this Message-ID (diff)
From: dthaler1968=40googlemail.com@dmarc.ietf.org
To: <bpf@vger.kernel.org>, <bpf@ietf.org>
Subject: [Bpf] Follow up on "call helper function by address" terminology
Date: Fri, 5 Apr 2024 13:10:38 -0700	[thread overview]
Message-ID: <0a0f01da8795$5496b250$fdc416f0$@gmail.com> (raw)
Message-ID: <20240405201038.j8-acn1GYq3WWUiXXwVsICOIw3-UkGojkfHZPQLFYXo@z> (raw)

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".

Thoughts, or other alternatives?

Dave

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

             reply	other threads:[~2024-04-05 20:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-05 20:10 dthaler1968 [this message]
2024-04-05 20:10 ` [Bpf] Follow up on "call helper function by address" terminology dthaler1968=40googlemail.com
2024-04-05 21:50 ` David Vernet
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='0a0f01da8795$5496b250$fdc416f0$@gmail.com' \
    --to=dthaler1968@googlemail.com \
    --cc=bpf@ietf.org \
    --cc=bpf@vger.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