DPDK usage discussions
 help / color / mirror / Atom feed
From: Avi Cohen <acohen@ves.io>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] eBPF in DPDK
Date: Mon, 8 Apr 2019 21:16:53 +0300	[thread overview]
Message-ID: <CAJGSrbPMH-MuWDzCWcZT-BF1=TAB5ZB1N_ZBujUdLmt5j2Bhpw@mail.gmail.com> (raw)
In-Reply-To: <20190408080903.7669aa11@shemminger-XPS-13-9360>

Stephen
I did not understand. Is this eBPF dpdk feature can run in the kernel or
userspace ?
Regards avi

בתאריך יום ב׳, 8 באפר׳ 2019, 18:09, מאת Stephen Hemminger ‏<
stephen@networkplumber.org>:

> On Mon, 8 Apr 2019 17:25:55 +0300
> Avi Cohen <acohen@ves.io> wrote:
>
> > Hi All,
> > can someone refer to the flow of a packet that is processed  in eBPF
> > program in the kernel . and then forwarded to DPDK-app in user space.
> > this was integrated into DPDK 18.05   but not documented. (
> > https://doc.dpdk.org/guides-18.05/prog_guide/bpf_lib.html)
> > what is the PMD type for this flow ? new socket ? what is the penalty ?
> > i thought to do some traffic filtering  there.
> > pros/cons ?
> > Best Regards
> > Avi
>
>
> Unlike Linux which has a predetermined set of steps in processing packets.
> DPDK is a raw toolkit where the processing is composed totally by the
> network application.
>
> Therefore DPDK has a raw eBPF library, it is up to the application to
> install it where
> it wants in the packet processing. One example is done via rx and tx
> callbacks
> as shown in the rte_bpf_ethdev.h.
>

  reply	other threads:[~2019-04-08 18:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08 14:25 Avi Cohen
2019-04-08 15:09 ` Stephen Hemminger
2019-04-08 18:16   ` Avi Cohen [this message]
2019-04-08 18:31     ` Stephen Hemminger
2019-04-08 18:37       ` Avi Cohen

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='CAJGSrbPMH-MuWDzCWcZT-BF1=TAB5ZB1N_ZBujUdLmt5j2Bhpw@mail.gmail.com' \
    --to=acohen@ves.io \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.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).