From: "Loftus, Ciara" <ciara.loftus@intel.com>
To: "Tahhan, Maryam" <maryam.tahhan@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/af_xdp: custom XDP program loading
Date: Mon, 14 Sep 2020 13:07:03 +0000 [thread overview]
Message-ID: <73c9bee78512408197592284e8d92485@intel.com> (raw)
In-Reply-To: <MN2PR11MB374312B68ABE8A4B2A9B9298F0270@MN2PR11MB3743.namprd11.prod.outlook.com>
> >
> > The new 'xdp_prog=<string>' vdev arg allows the user to specify the path
> to
> > a custom XDP program to be set on the device, instead of the default libbpf
> > one. The program must have an XSK_MAP of name 'xsks_map' which will
> > allow for the redirection of some packets to userspace and thus the PMD,
> > using some criteria defined in the program.
> > Note: a netdev may only load one program.
> >
> > Signed-off-by: Ciara Loftus <ciara.loftus@intel.com>
> > ---
>
> [MT] Stupid question :), AF_XDP is specifically related to loading an XDP
> program that allows you to redirect packets to an XSK...
> why would you want to allow a custom XDP program to be loaded?
>
> Other than that the code itself looked GTM
Hi Maryam,
Thanks for your feedback. It's a good question, and I will update the commit message in the v2 with the reasoning.
Sometimes it might be desired to redirect some not all packets to the xsk/PMD. eg. if the user wishes to drop or process a certain type of packet in the kernel. That logic can be put in the custom program. The key is that the custom program allows for *some* packets to still hit the xsk, and we check for that through checking the presence of the xsks_map.
Thanks,
Ciara
>
> <snip>
next prev parent reply other threads:[~2020-09-14 13:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-28 11:18 Ciara Loftus
2020-09-10 11:40 ` Tahhan, Maryam
2020-09-14 13:07 ` Loftus, Ciara [this message]
2020-09-18 2:54 ` Hu, Xuekun
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=73c9bee78512408197592284e8d92485@intel.com \
--to=ciara.loftus@intel.com \
--cc=dev@dpdk.org \
--cc=maryam.tahhan@intel.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).