RE: [Bpf] Follow up on "call helper function by address" terminology

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: RE: [Bpf] Follow up on "call helper function by address" terminology
From: dthaler1968@xxxxxxxxxxxxxx
Date: Thu, 18 Apr 2024 05:46:38 -0700
Cc: "'Watson Ladd'" <watsonbladd@xxxxxxxxx>, "'David Vernet'" <void@xxxxxxxxxxxxx>, <bpf@xxxxxxxxxxxxxxx>, <bpf@xxxxxxxx>
In-reply-to: <ZiDFRI3sdClyG-dj@infradead.org>
Thread-index: AQGym9lSVor9R6wjkVDgbvdbCMHIbgJp4F1KApIu0eEBfB5hlwKy7T0BsXSL+2A=

Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote:
> Maybe "static ID", or "pre-assigned" id?

I'd be ok with either of those. If I don't hear
otherwise, I'll create a patch using "static ID".

Dave

References:
- Follow up on "call helper function by address" terminology
  - From: dthaler1968
- Re: [Bpf] Follow up on "call helper function by address" terminology
  - From: David Vernet
- Re: [Bpf] Follow up on "call helper function by address" terminology
  - From: Watson Ladd
- RE: [Bpf] Follow up on "call helper function by address" terminology
  - From: dthaler1968
- Re: [Bpf] Follow up on "call helper function by address" terminology
  - From: Christoph Hellwig

Prev by Date: Re: [PATCH net-next v9] virtio_net: Support RX hash XDP hint
Next by Date: Re: [PATCH 1/2] [v2] net: ethernet: ti-cpsw: fix linking built-in code to modules
Previous by thread: Re: [Bpf] Follow up on "call helper function by address" terminology
Next by thread: [RFC PATCH bpf-next] verifier: fix computation of range for XOR
Index(es):
- Date
- Thread

[Index of Archives] [Linux Samsung SoC] [Linux Rockchip SoC] [Linux Actions SoC] [Linux for Synopsys ARC Processors] [Linux NFS] [Linux NILFS] [Linux USB Devel] [Video for Linux] [Linux Audio Users] [Yosemite News] [Linux Kernel] [Linux SCSI]

Powered by Linux