From: Martin KaFai Lau <martin.lau@linux.dev>
To: Daniel Borkmann <daniel@iogearbox.net>, bpf@vger.kernel.org
Cc: 'Alexei Starovoitov ' <ast@kernel.org>,
'Andrii Nakryiko ' <andrii@kernel.org>,
netdev@vger.kernel.org, kernel-team@meta.com
Subject: Re: [PATCH v2 bpf-next 1/2] bpf: Add BPF_FIB_LOOKUP_SKIP_NEIGH for bpf_fib_lookup
Date: Fri, 17 Feb 2023 12:34:56 -0800 [thread overview]
Message-ID: <d32b1c26-c401-1d07-bd8c-b71989b81ba6@linux.dev> (raw)
In-Reply-To: <1c275189-e693-18eb-444d-b125193af615@iogearbox.net>
On 2/17/23 12:34 PM, Daniel Borkmann wrote:
> On 2/17/23 7:12 PM, Martin KaFai Lau wrote:
> [...]
>> include/uapi/linux/bpf.h | 1 +
>> net/core/filter.c | 39 ++++++++++++++++++++++------------
>> tools/include/uapi/linux/bpf.h | 1 +
>> 3 files changed, 28 insertions(+), 13 deletions(-)
>>
>> diff --git a/include/uapi/linux/bpf.h b/include/uapi/linux/bpf.h
>> index 1503f61336b6..6c1956e36c97 100644
>> --- a/include/uapi/linux/bpf.h
>> +++ b/include/uapi/linux/bpf.h
>> @@ -6750,6 +6750,7 @@ struct bpf_raw_tracepoint_args {
>> enum {
>> BPF_FIB_LOOKUP_DIRECT = (1U << 0),
>> BPF_FIB_LOOKUP_OUTPUT = (1U << 1),
>> + BPF_FIB_LOOKUP_SKIP_NEIGH = (1U << 2),
>
> Sry, just noticed this now, but this would also need a uapi helper comment
> to describe the new BPF_FIB_LOOKUP_SKIP_NEIGH flag.
ah. right. will respin shortly.
prev parent reply other threads:[~2023-02-17 20:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 18:12 [PATCH v2 bpf-next 1/2] bpf: Add BPF_FIB_LOOKUP_SKIP_NEIGH for bpf_fib_lookup Martin KaFai Lau
2023-02-17 18:12 ` [PATCH v2 bpf-next 2/2] selftests/bpf: Add bpf_fib_lookup test Martin KaFai Lau
2023-02-17 20:34 ` [PATCH v2 bpf-next 1/2] bpf: Add BPF_FIB_LOOKUP_SKIP_NEIGH for bpf_fib_lookup Daniel Borkmann
2023-02-17 20:34 ` Martin KaFai Lau [this message]
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=d32b1c26-c401-1d07-bd8c-b71989b81ba6@linux.dev \
--to=martin.lau@linux.dev \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=kernel-team@meta.com \
--cc=netdev@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