All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Borkmann <daniel@iogearbox.net>
To: John Fastabend <john.fastabend@gmail.com>, ast@kernel.org
Cc: netdev@vger.kernel.org, davem@davemloft.net
Subject: Re: [bpf-next PATCH v3 0/4] bpf, sockmap BPF_F_INGRESS support
Date: Fri, 30 Mar 2018 22:53:21 +0200	[thread overview]
Message-ID: <57cbc0ad-fee5-643e-52c2-f47545518fe0@iogearbox.net> (raw)
In-Reply-To: <20180328194710.16072.99278.stgit@john-Precision-Tower-5810>

On 03/28/2018 09:49 PM, John Fastabend wrote:
> This series adds the BPF_F_INGRESS flag support to the redirect APIs.
> Bringing the sockmap API in-line with the cls_bpf redirect APIs.
> 
> We add it to both variants of sockmap programs, the first patch adds
> support for tx ulp hooks and the third patch adds support for the recv
> skb hooks. Patches two and four add tests for the corresponding
> ingress redirect hooks.
> 
> Follow on patches can address busy polling support, but next series
> from me will move the sockmap sample program into selftests.
> 
> v2: added static to function definition caught by kbuild bot
> v3: fixed an error branch with missing mem_uncharge
>     in recvmsg op moved receive_queue check outside of RCU region

Applied this yesterday to bpf-next, thanks John!

      parent reply	other threads:[~2018-03-30 20:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28 19:49 [bpf-next PATCH v3 0/4] bpf, sockmap BPF_F_INGRESS support John Fastabend
2018-03-28 19:49 ` [bpf-next PATCH v3 1/4] bpf: sockmap redirect ingress support John Fastabend
2018-03-28 19:49 ` [bpf-next PATCH v3 2/4] bpf: sockmap, add BPF_F_INGRESS tests John Fastabend
2018-03-28 19:49 ` [bpf-next PATCH v3 3/4] bpf: sockmap, BPF_F_INGRESS flag for BPF_SK_SKB_STREAM_VERDICT: John Fastabend
2018-03-28 19:49 ` [bpf-next PATCH v3 4/4] bpf: sockmap, more BPF_SK_SKB_STREAM_VERDICT tests John Fastabend
2018-03-30 20:53 ` Daniel Borkmann [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=57cbc0ad-fee5-643e-52c2-f47545518fe0@iogearbox.net \
    --to=daniel@iogearbox.net \
    --cc=ast@kernel.org \
    --cc=davem@davemloft.net \
    --cc=john.fastabend@gmail.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 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.