From: Martin KaFai Lau <kafai@fb.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: FB Kernel Team <kernel-team@fb.com>,
Alexei Starovoitov <alexei.starovoitov@gmail.com>
Subject: [PATCH net-next 0/4] bpf: bpf_htab: Add BPF_MAP_TYPE_PERCPU_HASH
Date: Thu, 7 Jan 2016 14:35:51 -0800 [thread overview]
Message-ID: <1452206155-1492617-1-git-send-email-kafai@fb.com> (raw)
This patchset adds BPF_MAP_TYPE_PERCPU_HASH map type which allows
percpu value.
BPF + kprobe is very useful in statistics collection. In particular,
bpf is strong in doing aggregation within the kernel instead of
outputting a lot of raw samples to the userspace.
In some cases, bumping a counter/value of a particular key will have
noticeable impact. For example, doing statistics collection
on received packets and aggregating them by network
prefix (like /64 in IPv6). Having a percpu value can help.
next reply other threads:[~2016-01-07 22:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 22:35 Martin KaFai Lau [this message]
2016-01-07 22:35 ` [PATCH net-next 1/4] bpf: bpf_htab: Refactor some htab_elem logic Martin KaFai Lau
2016-01-07 22:35 ` [PATCH net-next 2/4] bpf: bpf_htab: Add BPF_MAP_TYPE_PERCPU_HASH Martin KaFai Lau
2016-01-09 10:06 ` Ming Lei
2016-01-12 3:11 ` Martin KaFai Lau
2016-01-12 7:44 ` Martin KaFai Lau
2016-01-09 10:33 ` Ming Lei
2016-01-07 22:35 ` [PATCH net-next 3/4] bpf: bpf_htab: Add syscall to iterate percpu value of a key Martin KaFai Lau
2016-01-07 22:35 ` [PATCH net-next 4/4] bpf: bpf_htab: Test for BPF_MAP_TYPE_PERCPU_HASH Martin KaFai Lau
2016-01-08 6:55 ` [PATCH net-next 0/4] bpf: bpf_htab: Add BPF_MAP_TYPE_PERCPU_HASH Ming Lei
2016-01-09 0:44 ` Martin KaFai Lau
2016-01-09 9:39 ` Ming Lei
2016-01-10 2:30 ` Martin KaFai Lau
2016-01-11 2:20 ` Ming Lei
2016-01-11 22:35 ` Martin KaFai Lau
2016-01-12 5:48 ` Ming Lei
2016-01-12 6:00 ` 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=1452206155-1492617-1-git-send-email-kafai@fb.com \
--to=kafai@fb.com \
--cc=alexei.starovoitov@gmail.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).