From: Jesper Dangaard Brouer <brouer@redhat.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: brouer@redhat.com, Jakub Kicinski <jakub.kicinski@netronome.com>,
netdev@vger.kernel.org, Martin KaFai Lau <kafai@fb.com>
Subject: Re: [PATCH bpf-next v4 2/2] samples/bpf: Add xdp_sample_pkts example
Date: Wed, 6 Jun 2018 13:33:49 +0200 [thread overview]
Message-ID: <20180606133349.401f7cfe@redhat.com> (raw)
In-Reply-To: <87vaawyy8v.fsf@toke.dk>
On Wed, 06 Jun 2018 13:01:52 +0200
Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Jakub Kicinski <jakub.kicinski@netronome.com> writes:
>
> > On Tue, 05 Jun 2018 16:50:00 +0200, Toke Høiland-Jørgensen wrote:
> >> Add an example program showing how to sample packets from XDP using the
> >> perf event buffer. The example userspace program just prints the ethernet
> >> header for every packet sampled.
> >>
> >> Signed-off-by: Toke Høiland-Jørgensen <toke@toke.dk>
> >
> >> diff --git a/samples/bpf/xdp_sample_pkts_kern.c b/samples/bpf/xdp_sample_pkts_kern.c
> >> new file mode 100644
> >> index 000000000000..4560522ca015
> >> --- /dev/null
> >> +++ b/samples/bpf/xdp_sample_pkts_kern.c
> >> @@ -0,0 +1,62 @@
> >> +#include <linux/ptrace.h>
> >> +#include <linux/version.h>
> >> +#include <uapi/linux/bpf.h>
> >> +#include "bpf_helpers.h"
> >> +
> >> +#define SAMPLE_SIZE 64ul
> >> +#define MAX_CPUS 24
> >
> > That may be a lil' too few for modern HW with hyper-threading on ;)
> > My development machine says:
> >
> > $ ncpus
> > 28
> >
> > 128, maybe?
>
> What? 24 CPUs should be enough for everyone, surely? ;)
>
> (I just took twice the number of CPUs in my largest machine; but fair
> point, other people have access to more expensive toys I guess... will fix)
>
> >> +#define bpf_printk(fmt, ...) \
> >> +({ \
> >> + char ____fmt[] = fmt; \
> >> + bpf_trace_printk(____fmt, sizeof(____fmt), \
> >> + ##__VA_ARGS__); \
> >> +})
> >> +
> >> +struct bpf_map_def SEC("maps") my_map = {
> >> + .type = BPF_MAP_TYPE_PERF_EVENT_ARRAY,
> >> + .key_size = sizeof(int),
> >> + .value_size = sizeof(u32),
> >> + .max_entries = MAX_CPUS,
> >> +};
I agree, we should increase it to something larger than 24, just to
avoid people getting surprised, but this is only sample code.
At some point I want us to add another example, that show how to adjust
this runtime, which is actually possible with bpf_load.c via a map
callback that Martin added. I've not look at how libbpf can support
this. I do have sample code[1] that could be adjusted to do this, but
I don't want to create dependencies to bpf_load.c, as we all agree that
everything should be moved to use libbpf (tools/lib/bpf).
[1] https://github.com/netoptimizer/prototype-kernel/blob/master/kernel/samples/bpf/xdp_ddos01_blacklist_user.c#L186-L218
--
Best regards,
Jesper Dangaard Brouer
MSc.CS, Principal Kernel Engineer at Red Hat
LinkedIn: http://www.linkedin.com/in/brouer
next prev parent reply other threads:[~2018-06-06 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-05 14:50 [PATCH bpf-next v4 1/2] trace_helpers.c: Add helpers to poll multiple perf FDs for events Toke Høiland-Jørgensen
2018-06-05 14:50 ` [PATCH bpf-next v4 2/2] samples/bpf: Add xdp_sample_pkts example Toke Høiland-Jørgensen
2018-06-05 22:24 ` Jakub Kicinski
2018-06-06 11:01 ` Toke Høiland-Jørgensen
2018-06-06 11:33 ` Jesper Dangaard Brouer [this message]
2018-06-05 22:16 ` [PATCH bpf-next v4 1/2] trace_helpers.c: Add helpers to poll multiple perf FDs for events Jakub Kicinski
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=20180606133349.401f7cfe@redhat.com \
--to=brouer@redhat.com \
--cc=jakub.kicinski@netronome.com \
--cc=kafai@fb.com \
--cc=netdev@vger.kernel.org \
--cc=toke@toke.dk \
/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).