From: David Miller <davem@davemloft.net>
To: kafai@fb.com
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
alexei.starovoitov@gmail.com, tom.leiming@gmail.com,
kernel-team@fb.com
Subject: Re: [PATCH v2 net-next 0/4] bpf: bpf_htab: Add BPF_MAP_TYPE_PERCPU_HASH
Date: Tue, 12 Jan 2016 16:45:36 -0500 (EST) [thread overview]
Message-ID: <20160112.164536.17755595447757162.davem@davemloft.net> (raw)
In-Reply-To: <1452586852-1575604-1-git-send-email-kafai@fb.com>
From: Martin KaFai Lau <kafai@fb.com>
Date: Tue, 12 Jan 2016 00:20:48 -0800
> 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.
Please:
http://marc.info/?l=linux-netdev&m=145248145925834&w=2
Thanks.
prev parent reply other threads:[~2016-01-12 21:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 8:20 [PATCH v2 net-next 0/4] bpf: bpf_htab: Add BPF_MAP_TYPE_PERCPU_HASH Martin KaFai Lau
2016-01-12 8:20 ` [PATCH v2 net-next 1/4] bpf: bpf_htab: Refactor some htab_elem logic Martin KaFai Lau
2016-01-12 8:20 ` [PATCH v2 net-next 2/4] bpf: bpf_htab: Add BPF_MAP_TYPE_PERCPU_HASH Martin KaFai Lau
2016-01-12 8:20 ` [PATCH v2 net-next 3/4] bpf: bpf_htab: Add syscall to iterate percpu value of a key Martin KaFai Lau
2016-01-13 2:24 ` Eric Dumazet
2016-01-13 2:42 ` Ming Lei
2016-01-13 5:23 ` Alexei Starovoitov
2016-01-13 15:43 ` Ming Lei
2016-01-14 1:24 ` Alexei Starovoitov
2016-01-14 3:23 ` Ming Lei
2016-01-12 8:20 ` [PATCH v2 net-next 4/4] bpf: bpf_htab: Test for BPF_MAP_TYPE_PERCPU_HASH Martin KaFai Lau
2016-01-12 21:45 ` David Miller [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=20160112.164536.17755595447757162.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=kafai@fb.com \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=tom.leiming@gmail.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).