From: Johannes Berg <johannes@sipsolutions.net>
To: netdev@vger.kernel.org
Cc: Alexei Starovoitov <ast@kernel.org>,
Daniel Borkmann <daniel@iogearbox.net>
Subject: Re: [PATCH 1/2] bpf: remove struct bpf_prog_type_list
Date: Tue, 04 Apr 2017 19:32:30 +0200 [thread overview]
Message-ID: <1491327150.26929.3.camel@sipsolutions.net> (raw)
In-Reply-To: <20170404172711.4088-1-johannes@sipsolutions.net> (sfid-20170404_192734_554753_EB507E8D)
Oops, I really meant to send these as RFC more than anything, because I
don't really understand why it's done that way :)
FWIW, the bloat-o-meter looks similar in both cases, like this:
add/remove: 0/11 grow/shrink: 9/1 up/down: 145/-365 (-220)
function old new delta
bpf_map_types 16 96 +80
register_htab_map 56 76 +20
register_array_map 32 42 +10
bpf_register_map_type 35 45 +10
register_trie_map 20 25 +5
register_stack_map 20 25 +5
register_prog_array_map 20 25 +5
register_perf_event_array_map 20 25 +5
register_cgroup_array_map 20 25 +5
sys_bpf 1140 1127 -13
trie_type 32 - -32
stack_map_type 32 - -32
prog_array_type 32 - -32
perf_event_array_type 32 - -32
percpu_array_type 32 - -32
htab_type 32 - -32
htab_percpu_type 32 - -32
htab_lru_type 32 - -32
htab_lru_percpu_type 32 - -32
cgroup_array_type 32 - -32
array_type 32 - -32
johannes
next prev parent reply other threads:[~2017-04-04 17:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-04 17:27 [PATCH 1/2] bpf: remove struct bpf_prog_type_list Johannes Berg
2017-04-04 17:27 ` [PATCH 2/2] bpf: remove struct bpf_map_type_list Johannes Berg
2017-04-04 17:32 ` Johannes Berg [this message]
2017-04-05 17:57 ` [PATCH 1/2] bpf: remove struct bpf_prog_type_list 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=1491327150.26929.3.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--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 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.