Netdev List
 help / color / mirror / Atom feed
From: John Fastabend <john.fastabend@gmail.com>
To: ast@kernel.org, daniel@iogearbox.net
Cc: netdev@vger.kernel.org
Subject: [bpf-next PATCH 0/3] sockmap support for msg_peek flag
Date: Tue, 16 Oct 2018 11:07:54 -0700	[thread overview]
Message-ID: <20181016180424.13607.7932.stgit@john-Precision-Tower-5810> (raw)

This adds support for the MSG_PEEK flag when redirecting into an
ingress psock sk_msg queue.

The first patch adds some base support to the helpers, then the
feature, and finally we add an option for the test suite to do
a duplicate MSG_PEEK call on every recv to test the feature.

With duplicate MSG_PEEK call all tests continue to PASS.

---

John Fastabend (3):
      bpf: skmsg, improve sk_msg_used_element to work in cork context
      bpf: sockmap, support for msg_peek in sk_msg with redirect ingress
      bpf: sockmap, add msg_peek tests to test_sockmap


 include/linux/skmsg.h                      |   13 +-
 include/net/tcp.h                          |    2 
 net/ipv4/tcp_bpf.c                         |   42 +++++--
 net/tls/tls_sw.c                           |    3 -
 tools/testing/selftests/bpf/test_sockmap.c |  167 +++++++++++++++++++---------
 5 files changed, 153 insertions(+), 74 deletions(-)

             reply	other threads:[~2018-10-17  1:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-16 18:07 John Fastabend [this message]
2018-10-16 18:07 ` [bpf-next PATCH 1/3] bpf: skmsg, improve sk_msg_used_element to work in cork context John Fastabend
2018-10-16 18:08 ` [bpf-next PATCH 2/3] bpf: sockmap, support for msg_peek in sk_msg with redirect ingress John Fastabend
2018-10-16 18:08 ` [bpf-next PATCH 3/3] bpf: sockmap, add msg_peek tests to test_sockmap John Fastabend
2018-10-16 18:41 ` [bpf-next PATCH 0/3] sockmap support for msg_peek flag Alexei Starovoitov
2018-10-17  0:32   ` Daniel Borkmann

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=20181016180424.13607.7932.stgit@john-Precision-Tower-5810 \
    --to=john.fastabend@gmail.com \
    --cc=ast@kernel.org \
    --cc=daniel@iogearbox.net \
    --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