All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Song Liu <liu.song.a23@gmail.com>
Cc: Networking <netdev@vger.kernel.org>
Subject: Re: [PATCH] samples/bpf: Add xdp_sample_pkts example
Date: Thu, 31 May 2018 11:44:17 +0200	[thread overview]
Message-ID: <87a7sgcg7i.fsf@toke.dk> (raw)
In-Reply-To: <CAPhsuW4ZKvJRjy-==j6ZzeAY0UF+X+aMrSNz0KCYLqM-zpmssA@mail.gmail.com>

Song Liu <liu.song.a23@gmail.com> writes:

> On Wed, May 30, 2018 at 9:45 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>> This adds 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.
>>
>> Most of the userspace code is borrowed from other examples, most notably
>> trace_output.
>>
>> Note that the example only works when everything runs on CPU0; so
>> suitable smp_affinity needs to be set on the device. Some drivers seem
>> to reset smp_affinity when loading an XDP program, so it may be
>> necessary to change it after starting the example userspace program.
>
> Why does this only works when everything runs on CPU0? Is this
> something we can improve?

Yeah, good question. Basically, the call from XDP to
bpf_perf_event_output() will fail with -EOPNOTSUPP. I tracked this down
to this if statement in __bpf_perf_event_output() in bpf_trace.c:

>	if (unlikely(event->oncpu != cpu))
>		return -EOPNOTSUPP;

I *think* that the way to fix this is for the userspace program to open
a perf file descriptor for each CPU in the system and poll all of them,
in which case the XDP program can pass the BPF_F_CURRENT_CPU flag to
access the right one. I would love for someone more knowledgeable about
perf internals to confirm this, though.

And, well, the polling function in trace_helpers.c doesn't support
currently this, and I didn't have the time to fix that while writing
this example :)

-Toke

  reply	other threads:[~2018-05-31  9:44 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 16:45 [PATCH] samples/bpf: Add xdp_sample_pkts example Toke Høiland-Jørgensen
2018-05-31  5:03 ` Song Liu
2018-05-31  9:44   ` Toke Høiland-Jørgensen [this message]
2018-06-02  4:22     ` Daniel Borkmann
2018-06-04 12:31       ` Daniel Borkmann
2018-06-04 13:02         ` Toke Høiland-Jørgensen
2018-06-04 13:12           ` Daniel Borkmann

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=87a7sgcg7i.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=liu.song.a23@gmail.com \
    --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.