[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9e620507-6e9b-16f8-5ef9-3bbf2c2b6a3c@iogearbox.net>
Date: Fri, 26 Feb 2021 23:34:34 +0100
From: Daniel Borkmann <daniel@...earbox.net>
To: Jesper Dangaard Brouer <brouer@...hat.com>, bpf@...r.kernel.org
Cc: netdev@...r.kernel.org, Daniel Borkmann <borkmann@...earbox.net>,
Alexei Starovoitov <alexei.starovoitov@...il.com>
Subject: Re: [PATCH bpf-next V2 0/2] bpf: Updates for BPF-helper bpf_check_mtu
On 2/19/21 7:36 AM, Jesper Dangaard Brouer wrote:
> On Thu, 18 Feb 2021 12:49:53 +0100
> Jesper Dangaard Brouer <brouer@...hat.com> wrote:
>
>> The FIB lookup example[1] show how the IP-header field tot_len
>> (iph->tot_len) is used as input to perform the MTU check. The recently
>> added MTU check helper bpf_check_mtu() should also support this type
>> of MTU check.
>>
>> Lets add this feature before merge window, please. This is a followup
>> to 34b2021cc616 ("bpf: Add BPF-helper for MTU checking").
>
> Which git tree should I send this against bpf-next or bpf, to keep this
> change together with 34b2021cc616 ("bpf: Add BPF-helper for MTU
> checking") ?
Given this is an api change, we'll take this into bpf tree after the
pending pr was merged.
Powered by blists - more mailing lists