All of lore.kernel.org
 help / color / mirror / Atom feed
From: sdf at google.com (Stanislav Fomichev)
Subject: [PATCH v2 bpf-next 0/3] bpftool: support loading flow dissector
Date: Wed,  7 Nov 2018 14:43:53 -0800	[thread overview]
Message-ID: <20181107224356.73080-1-sdf@google.com> (raw)

v2 changes:
* addressed comments/style issues from Jakub Kicinski & Quentin Monnet
* removed logic that populates jump table
* added cleanup for partial failure in bpf_object__pin

This patch series adds support for loading and attaching flow dissector
programs from the bpftool:

* first patch fixes flow dissector section name in the selftests (so
  libbpf auto-detection works)
* second patch adds proper cleanup to bpf_object__pin which is now being
  used to attach all flow dissector progs/maps
* third patch adds actual support to the bpftool

See third patch for the description/details.

Stanislav Fomichev (3):
  selftests/bpf: rename flow dissector section to flow_dissector
  libbpf: cleanup after partial failure in bpf_object__pin
  bpftool: support loading flow dissector

 .../bpftool/Documentation/bpftool-prog.rst    | 26 +++--
 tools/bpf/bpftool/bash-completion/bpftool     |  2 +-
 tools/bpf/bpftool/common.c                    | 30 +++---
 tools/bpf/bpftool/main.h                      |  1 +
 tools/bpf/bpftool/prog.c                      | 94 ++++++++++++++-----
 tools/lib/bpf/libbpf.c                        | 58 ++++++++++--
 tools/testing/selftests/bpf/bpf_flow.c        |  2 +-
 .../selftests/bpf/test_flow_dissector.sh      |  2 +-
 8 files changed, 151 insertions(+), 64 deletions(-)

-- 
2.19.1.930.g4563a0d9d0-goog

WARNING: multiple messages have this Message-ID (diff)
From: sdf@google.com (Stanislav Fomichev)
Subject: [PATCH v2 bpf-next 0/3] bpftool: support loading flow dissector
Date: Wed,  7 Nov 2018 14:43:53 -0800	[thread overview]
Message-ID: <20181107224356.73080-1-sdf@google.com> (raw)
Message-ID: <20181107224353.bEqWCX3cD4S0xAs8dWov6t_00PLNujj0SlTyp0AAw0M@z> (raw)

v2 changes:
* addressed comments/style issues from Jakub Kicinski & Quentin Monnet
* removed logic that populates jump table
* added cleanup for partial failure in bpf_object__pin

This patch series adds support for loading and attaching flow dissector
programs from the bpftool:

* first patch fixes flow dissector section name in the selftests (so
  libbpf auto-detection works)
* second patch adds proper cleanup to bpf_object__pin which is now being
  used to attach all flow dissector progs/maps
* third patch adds actual support to the bpftool

See third patch for the description/details.

Stanislav Fomichev (3):
  selftests/bpf: rename flow dissector section to flow_dissector
  libbpf: cleanup after partial failure in bpf_object__pin
  bpftool: support loading flow dissector

 .../bpftool/Documentation/bpftool-prog.rst    | 26 +++--
 tools/bpf/bpftool/bash-completion/bpftool     |  2 +-
 tools/bpf/bpftool/common.c                    | 30 +++---
 tools/bpf/bpftool/main.h                      |  1 +
 tools/bpf/bpftool/prog.c                      | 94 ++++++++++++++-----
 tools/lib/bpf/libbpf.c                        | 58 ++++++++++--
 tools/testing/selftests/bpf/bpf_flow.c        |  2 +-
 .../selftests/bpf/test_flow_dissector.sh      |  2 +-
 8 files changed, 151 insertions(+), 64 deletions(-)

-- 
2.19.1.930.g4563a0d9d0-goog

WARNING: multiple messages have this Message-ID (diff)
From: Stanislav Fomichev <sdf@google.com>
To: netdev@vger.kernel.org, linux-kselftest@vger.kernel.org,
	ast@kernel.org, daniel@iogearbox.net, shuah@kernel.org,
	jakub.kicinski@netronome.com, quentin.monnet@netronome.com
Cc: guro@fb.com, jiong.wang@netronome.com, sdf@google.com,
	bhole_prashant_q7@lab.ntt.co.jp, john.fastabend@gmail.com,
	jbenc@redhat.com, treeze.taeung@gmail.com, yhs@fb.com,
	osk@fb.com, sandipan@linux.vnet.ibm.com
Subject: [PATCH v2 bpf-next 0/3] bpftool: support loading flow dissector
Date: Wed,  7 Nov 2018 14:43:53 -0800	[thread overview]
Message-ID: <20181107224356.73080-1-sdf@google.com> (raw)

v2 changes:
* addressed comments/style issues from Jakub Kicinski & Quentin Monnet
* removed logic that populates jump table
* added cleanup for partial failure in bpf_object__pin

This patch series adds support for loading and attaching flow dissector
programs from the bpftool:

* first patch fixes flow dissector section name in the selftests (so
  libbpf auto-detection works)
* second patch adds proper cleanup to bpf_object__pin which is now being
  used to attach all flow dissector progs/maps
* third patch adds actual support to the bpftool

See third patch for the description/details.

Stanislav Fomichev (3):
  selftests/bpf: rename flow dissector section to flow_dissector
  libbpf: cleanup after partial failure in bpf_object__pin
  bpftool: support loading flow dissector

 .../bpftool/Documentation/bpftool-prog.rst    | 26 +++--
 tools/bpf/bpftool/bash-completion/bpftool     |  2 +-
 tools/bpf/bpftool/common.c                    | 30 +++---
 tools/bpf/bpftool/main.h                      |  1 +
 tools/bpf/bpftool/prog.c                      | 94 ++++++++++++++-----
 tools/lib/bpf/libbpf.c                        | 58 ++++++++++--
 tools/testing/selftests/bpf/bpf_flow.c        |  2 +-
 .../selftests/bpf/test_flow_dissector.sh      |  2 +-
 8 files changed, 151 insertions(+), 64 deletions(-)

-- 
2.19.1.930.g4563a0d9d0-goog

             reply	other threads:[~2018-11-07 22:43 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-07 22:43 sdf [this message]
2018-11-07 22:43 ` [PATCH v2 bpf-next 0/3] bpftool: support loading flow dissector Stanislav Fomichev
2018-11-07 22:43 ` Stanislav Fomichev
2018-11-07 22:43 ` [PATCH bpf-next 1/3] selftests/bpf: rename flow dissector section to flow_dissector sdf
2018-11-07 22:43   ` Stanislav Fomichev
2018-11-07 22:43   ` Stanislav Fomichev
2018-11-07 22:43 ` [PATCH bpf-next 2/3] libbpf: cleanup after partial failure in bpf_object__pin sdf
2018-11-07 22:43   ` Stanislav Fomichev
2018-11-07 22:43   ` Stanislav Fomichev
2018-11-07 22:56   ` jakub.kicinski
2018-11-07 22:56     ` Jakub Kicinski
2018-11-07 22:56     ` Jakub Kicinski
2018-11-07 23:00     ` sdf
2018-11-07 23:00       ` Stanislav Fomichev
2018-11-07 23:00       ` Stanislav Fomichev
2018-11-07 23:06       ` jakub.kicinski
2018-11-07 23:06         ` Jakub Kicinski
2018-11-07 23:06         ` Jakub Kicinski
2018-11-07 23:25         ` sdf
2018-11-07 23:25           ` Stanislav Fomichev
2018-11-07 23:25           ` Stanislav Fomichev
2018-11-07 23:38           ` jakub.kicinski
2018-11-07 23:38             ` Jakub Kicinski
2018-11-07 23:38             ` Jakub Kicinski
2018-11-07 22:43 ` [PATCH bpf-next 3/3] bpftool: support loading flow dissector sdf
2018-11-07 22:43   ` Stanislav Fomichev
2018-11-07 22:43   ` Stanislav Fomichev
2018-11-07 23:09   ` jakub.kicinski
2018-11-07 23:09     ` Jakub Kicinski
2018-11-07 23:09     ` Jakub Kicinski
2018-11-07 23:13     ` sdf
2018-11-07 23:13       ` Stanislav Fomichev
2018-11-07 23:13       ` Stanislav Fomichev
2018-11-07 23:29       ` jakub.kicinski
2018-11-07 23:29         ` Jakub Kicinski
2018-11-07 23:29         ` Jakub Kicinski
2018-11-07 23:34         ` sdf
2018-11-07 23:34           ` Stanislav Fomichev
2018-11-07 23:34           ` Stanislav Fomichev
2018-11-07 23:41           ` jakub.kicinski
2018-11-07 23:41             ` Jakub Kicinski
2018-11-07 23:41             ` Jakub Kicinski
2018-11-08  0:40             ` sdf
2018-11-08  0:40               ` Stanislav Fomichev
2018-11-08  0:40               ` Stanislav Fomichev

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=20181107224356.73080-1-sdf@google.com \
    --to=unknown@example.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 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.