bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Willem de Bruijn <willemdebruijn.kernel@gmail.com>
To: bpf@vger.kernel.org
Cc: netdev@vger.kernel.org, daniel@iogearbox.net, ast@kernel.org,
	Willem de Bruijn <willemb@google.com>
Subject: [PATCH bpf-next 0/3] add gso_size to __sk_buff
Date: Tue,  3 Mar 2020 15:05:00 -0500	[thread overview]
Message-ID: <20200303200503.226217-1-willemdebruijn.kernel@gmail.com> (raw)

From: Willem de Bruijn <willemb@google.com>

See first patch for details.

Patch split across three parts { kernel feature, uapi header, tools }
following the custom for such __sk_buff changes.

Willem de Bruijn (3):
  bpf: add gso_size to __sk_buff
  bpf: Sync uapi bpf.h to tools/
  selftests/bpf: test new __sk_buff field gso_size

 include/uapi/linux/bpf.h                      |  1 +
 net/bpf/test_run.c                            |  7 +++
 net/core/filter.c                             | 44 +++++++++++------
 tools/include/uapi/linux/bpf.h                |  1 +
 .../selftests/bpf/prog_tests/skb_ctx.c        |  1 +
 .../selftests/bpf/progs/test_skb_ctx.c        |  2 +
 .../testing/selftests/bpf/verifier/ctx_skb.c  | 47 +++++++++++++++++++
 7 files changed, 89 insertions(+), 14 deletions(-)

-- 
2.25.0.265.gbab2e86ba0-goog


             reply	other threads:[~2020-03-03 20:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-03 20:05 Willem de Bruijn [this message]
2020-03-03 20:05 ` [PATCH bpf-next 1/3] bpf: add gso_size to __sk_buff Willem de Bruijn
2020-03-03 20:05 ` [PATCH bpf-next 2/3] bpf: Sync uapi bpf.h to tools/ Willem de Bruijn
2020-03-03 20:05 ` [PATCH bpf-next 3/3] selftests/bpf: test new __sk_buff field gso_size Willem de Bruijn
2020-03-03 22:56 ` [PATCH bpf-next 0/3] add gso_size to __sk_buff Petar Penkov
2020-03-04  0:31   ` Alexei Starovoitov

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=20200303200503.226217-1-willemdebruijn.kernel@gmail.com \
    --to=willemdebruijn.kernel@gmail.com \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=netdev@vger.kernel.org \
    --cc=willemb@google.com \
    /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;
as well as URLs for NNTP newsgroup(s).