bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Bianconi <lorenzo@kernel.org>
To: bpf@vger.kernel.org, netdev@vger.kernel.org
Cc: ast@kernel.org, davem@davemloft.net, brouer@redhat.com,
	daniel@iogearbox.net, lorenzo.bianconi@redhat.com,
	dsahern@kernel.org
Subject: [RFC bpf-next 0/2] introduce support for XDP programs in cpumaps
Date: Fri, 22 May 2020 18:11:30 +0200	[thread overview]
Message-ID: <cover.1590162098.git.lorenzo@kernel.org> (raw)

Similar to what David Ahern proposed here [1] for DEVMAPs, introduce the
capability to attach and run a XDP program to cpumap entries.
The idea behind this feature is to add the possibility to define on which CPU
run the eBPF program if the underlying hw does not support RSS.
Even if the series is functional, at the moment some bit are missing
(e.g XDP_REDIRECT support or defining a new attach type).
The goal of this series is to get feebacks to add missing features.

[1] https://patchwork.ozlabs.org/project/netdev/cover/20200522010526.14649-1-dsahern@kernel.org/

Lorenzo Bianconi (2):
  bpf: cpumap: add the possibility to attach a eBPF program to cpumap
  samples/bpf: xdp_redirect_cpu: load a eBPF program on cpu_map

 kernel/bpf/cpumap.c                 | 111 +++++++++++++++++++++++-----
 samples/bpf/xdp_redirect_cpu_kern.c |  24 +++++-
 samples/bpf/xdp_redirect_cpu_user.c |  83 +++++++++++++++++----
 3 files changed, 185 insertions(+), 33 deletions(-)

-- 
2.26.2


             reply	other threads:[~2020-05-22 16:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-22 16:11 Lorenzo Bianconi [this message]
2020-05-22 16:11 ` [RFC bpf-next 1/2] bpf: cpumap: add the possibility to attach a eBPF program to cpumap Lorenzo Bianconi
2020-05-22 17:44   ` David Ahern
2020-05-22 17:54     ` Jesper Dangaard Brouer
2020-05-24 17:22   ` David Ahern
2020-05-22 16:11 ` [RFC bpf-next 2/2] samples/bpf: xdp_redirect_cpu: load a eBPF program on cpu_map Lorenzo Bianconi

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=cover.1590162098.git.lorenzo@kernel.org \
    --to=lorenzo@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=brouer@redhat.com \
    --cc=daniel@iogearbox.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=lorenzo.bianconi@redhat.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 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).