From: dthaler1968@googlemail.com
To: "'Watson Ladd'" <watsonbladd@gmail.com>,
"'David Vernet'" <void@manifault.com>
Cc: <dthaler1968=40googlemail.com@dmarc.ietf.org>,
<bpf@vger.kernel.org>, <bpf@ietf.org>
Subject: RE: [Bpf] Follow up on "call helper function by address" terminology
Date: Sun, 7 Apr 2024 09:23:33 -0700 [thread overview]
Message-ID: <003001da8907$efd41140$cf7c33c0$@gmail.com> (raw)
In-Reply-To: <CACsn0cmWzT4-+g0w0-ETC5ZMC1hdW0v-Rh1ZNCG2O23m9YCALQ@mail.gmail.com>
Watson Ladd wrote:
> On Fri, Apr 5, 2024 at 2:50 PM David Vernet <void@manifault.com> wrote:
> > 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?
>
> If something later comes along supplanting BTF it will be the not-BTF not-non-
> BTF thing. This is bad. How about untyped identifiers?
For runtimes that have a way to look up type info from a non-BTF ID, the
ID is not "untyped" per se.
Other possibilities:
* Classic ID, but "classic" would imply classic BPF
* Index, but that would imply the runtime actually has to implement it as an index
As such, I think "non-BTF ID" is better than the other possibilities above, and a
future ISA version could always rename it if other things come up in the future
that necessitate a terminology change.
Dave
WARNING: multiple messages have this Message-ID (diff)
From: dthaler1968=40googlemail.com@dmarc.ietf.org
To: "'Watson Ladd'" <watsonbladd@gmail.com>,
"'David Vernet'" <void@manifault.com>
Cc: <dthaler1968=40googlemail.com@dmarc.ietf.org>,
<bpf@vger.kernel.org>, <bpf@ietf.org>
Subject: Re: [Bpf] Follow up on "call helper function by address" terminology
Date: Sun, 7 Apr 2024 09:23:33 -0700 [thread overview]
Message-ID: <003001da8907$efd41140$cf7c33c0$@gmail.com> (raw)
Message-ID: <20240407162333.cS5jYz8JYBxW9LrXdj5RqdFTvacqEuSROfSVeMztM7A@z> (raw)
In-Reply-To: <CACsn0cmWzT4-+g0w0-ETC5ZMC1hdW0v-Rh1ZNCG2O23m9YCALQ@mail.gmail.com>
Watson Ladd wrote:
> On Fri, Apr 5, 2024 at 2:50 PM David Vernet <void@manifault.com> wrote:
> > 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?
>
> If something later comes along supplanting BTF it will be the not-BTF not-non-
> BTF thing. This is bad. How about untyped identifiers?
For runtimes that have a way to look up type info from a non-BTF ID, the
ID is not "untyped" per se.
Other possibilities:
* Classic ID, but "classic" would imply classic BPF
* Index, but that would imply the runtime actually has to implement it as an index
As such, I think "non-BTF ID" is better than the other possibilities above, and a
future ISA version could always rename it if other things come up in the future
that necessitate a terminology change.
Dave
--
Bpf mailing list
Bpf@ietf.org
https://www.ietf.org/mailman/listinfo/bpf
next prev parent reply other threads:[~2024-04-07 16:23 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
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 [this message]
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='003001da8907$efd41140$cf7c33c0$@gmail.com' \
--to=dthaler1968@googlemail.com \
--cc=bpf@ietf.org \
--cc=bpf@vger.kernel.org \
--cc=dthaler1968=40googlemail.com@dmarc.ietf.org \
--cc=void@manifault.com \
--cc=watsonbladd@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 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.