From: Jesper Dangaard Brouer <brouer@redhat.com>
To: bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, Daniel Borkmann <borkmann@iogearbox.net>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>,
maze@google.com, lmb@cloudflare.com, shaun@tigera.io,
Lorenzo Bianconi <lorenzo@kernel.org>,
marek@cloudflare.com, John Fastabend <john.fastabend@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
eyal.birger@gmail.com, colrack@gmail.com, brouer@redhat.com
Subject: Re: [PATCH bpf-next V6 0/7] Series short description
Date: Wed, 18 Nov 2020 16:37:10 +0100 [thread overview]
Message-ID: <20201118163710.201853da@carbon> (raw)
In-Reply-To: <160571329106.2801162.7380460134461487044.stgit@firesoul>
Sorry, please ignore this email.
(Wrong invocation of stg mail from command line)
--Jesper
On Wed, 18 Nov 2020 16:28:21 +0100
Jesper Dangaard Brouer <brouer@redhat.com> wrote:
> The following series implements...
>
> ---
>
> Jesper Dangaard Brouer (7):
> bpf: Remove MTU check in __bpf_skb_max_len
> bpf: fix bpf_fib_lookup helper MTU check for SKB ctx
> bpf: bpf_fib_lookup return MTU value as output when looked up
> bpf: add BPF-helper for MTU checking
> bpf: drop MTU check when doing TC-BPF redirect to ingress
> bpf: make it possible to identify BPF redirected SKBs
> selftests/bpf: use bpf_check_mtu in selftest test_cls_redirect
>
>
> .../selftests/bpf/progs/test_cls_redirect.c | 7 +++++++
> 1 file changed, 7 insertions(+)
>
> --
> Signature
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
prev parent reply other threads:[~2020-11-18 15:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-18 15:28 [PATCH bpf-next V6 0/7] Series short description Jesper Dangaard Brouer
2020-11-18 15:37 ` Jesper Dangaard Brouer [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=20201118163710.201853da@carbon \
--to=brouer@redhat.com \
--cc=alexei.starovoitov@gmail.com \
--cc=borkmann@iogearbox.net \
--cc=bpf@vger.kernel.org \
--cc=colrack@gmail.com \
--cc=eyal.birger@gmail.com \
--cc=john.fastabend@gmail.com \
--cc=kuba@kernel.org \
--cc=lmb@cloudflare.com \
--cc=lorenzo@kernel.org \
--cc=marek@cloudflare.com \
--cc=maze@google.com \
--cc=netdev@vger.kernel.org \
--cc=shaun@tigera.io \
/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.