From: Daniel Borkmann <daniel@iogearbox.net>
To: Jakub Kicinski <jakub.kicinski@netronome.com>,
alexei.starovoitov@gmail.com
Cc: oss-drivers@netronome.com, netdev@vger.kernel.org
Subject: Re: [PATCH bpf-next 0/8] tools: bpf: updates to bpftool and libbpf
Date: Sun, 1 Jul 2018 01:03:59 +0200 [thread overview]
Message-ID: <951108ab-a970-e30e-0d0b-b93503b664e1@iogearbox.net> (raw)
In-Reply-To: <20180628214142.11268-1-jakub.kicinski@netronome.com>
On 06/28/2018 11:41 PM, Jakub Kicinski wrote:
> Hi!
>
> Set of random updates to bpftool and libbpf. I'm preparing for
> extending bpftool prog load, but there is a good number of
> improvements that can be made before bpf -> bpf-next merge
> helping to keep the later patch set to a manageable size as well.
>
> First patch is a bpftool build speed improvement. Next missing
> program types are added to libbpf program type detection by section
> name. The ability to load programs from '.text' section is restored
> when ELF file doesn't contain any pseudo calls.
>
> In bpftool I remove my Author comments as unnecessary sign of vanity.
> Last but not least missing option is added to bash completions and
> processing of options in bash completions is improved.
Applied to bpf-next, thanks Jakub!
prev parent reply other threads:[~2018-06-30 23:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-28 21:41 [PATCH bpf-next 0/8] tools: bpf: updates to bpftool and libbpf Jakub Kicinski
2018-06-28 21:41 ` [PATCH bpf-next 1/8] tools: bpftool: use correct make variable type to improve compilation time Jakub Kicinski
2018-06-28 21:41 ` [PATCH bpf-next 2/8] tools: libbpf: add section names for missing program types Jakub Kicinski
2018-06-28 21:41 ` [PATCH bpf-next 3/8] tools: libbpf: allow setting ifindex for programs and maps Jakub Kicinski
2018-06-28 21:41 ` [PATCH bpf-next 4/8] tools: libbpf: restore the ability to load programs from .text section Jakub Kicinski
2018-06-28 21:41 ` [PATCH bpf-next 5/8] tools: libbpf: don't return '.text' as a program for multi-function programs Jakub Kicinski
2018-06-28 21:41 ` [PATCH bpf-next 6/8] tools: bpftool: drop unnecessary Author comments Jakub Kicinski
2018-06-28 21:41 ` [PATCH bpf-next 7/8] tools: bpftool: add missing --bpffs to completions Jakub Kicinski
2018-06-28 21:41 ` [PATCH bpf-next 8/8] tools: bpftool: deal with options upfront Jakub Kicinski
2018-06-30 23:03 ` 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=951108ab-a970-e30e-0d0b-b93503b664e1@iogearbox.net \
--to=daniel@iogearbox.net \
--cc=alexei.starovoitov@gmail.com \
--cc=jakub.kicinski@netronome.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@netronome.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