DPDK usage discussions
 help / color / mirror / Atom feed
From: george.dit@gmail.com
To: Shahaf Shuler <shahafs@mellanox.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] DPDK application that sends rules to the NIC
Date: Thu, 14 Sep 2017 04:37:05 -0700	[thread overview]
Message-ID: <CAN9HtFBW1eoMjS1LttvMb_Gc-8RiVqTyb2+vvteUB8yjikXQkg@mail.gmail.com> (raw)
In-Reply-To: <VI1PR05MB3149B2E601411848359AD202C36F0@VI1PR05MB3149.eurprd05.prod.outlook.com>

Hi Shahaf,

Thanks for the information, I am looking into it :)
I had some compilation issues when trying to port rte_flow from DPDK 17.02
into an external application but these issues go away if I use 17.08.

Best regards,
Georgios

On Thu, Sep 14, 2017 at 3:26 AM, Shahaf Shuler <shahafs@mellanox.com> wrote:

> Hi Georgios,
>
> Wednesday, September 13, 2017 11:09 AM, Georgios Katsikas:
> > Hi all,
> >
> > I would like to implement a DPDK application that dumps a set of rules
> to a
> > Mellanox ConnectX-5 NIC and starts a number of threads (each on a
> > different
> > core) that receive the classified packets according to the rules.
> > The rules are of the form src IP X and dst IP Y --> Send to core Z.
> >
> > Is there such an application (or similar) in the source tree?
>
> You can use testpmd for that. Run in isolate mode and add rte_flow rules
> to direct IP packets to the specific queue that you want.
>
> > Does the Mellanox
> > NIC require any special treatment or is there a unified API to do this
> job
> > regardless of the NIC?
>
> There Is a unified API. look into rte_flow:
> http://dpdk.org/doc/guides/prog_guide/rte_flow.html
>
> > Which DPDK version do you propose?
>
> The latest one - v17.08
>
> >
> > Thanks,
> > --
> > Georgios Katsikas
> > Industrial Ph.D. Student
> > Network Intelligence Group
> > Decision, Networks, and Analytics (DNA) Lab RISE SICS
> > E-Mail:  georgios.katsikas@ri.se
>



-- 
Georgios Katsikas
Industrial Ph.D. Student
Network Intelligence Group
Decision, Networks, and Analytics (DNA) Lab
RISE SICS
E-Mail:  georgios.katsikas@ri.se

  reply	other threads:[~2017-09-14 11:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-13  8:08 george.dit
2017-09-14 10:26 ` Shahaf Shuler
2017-09-14 11:37   ` george.dit [this message]
2017-09-18 12:26     ` george.dit
2017-09-18 13:20       ` Nélio Laranjeiro
2017-09-18 13:38         ` george.dit
2017-09-18 14:55           ` Nélio Laranjeiro
2017-09-18 14:58             ` george.dit
2017-09-19  9:43               ` george.dit

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=CAN9HtFBW1eoMjS1LttvMb_Gc-8RiVqTyb2+vvteUB8yjikXQkg@mail.gmail.com \
    --to=george.dit@gmail.com \
    --cc=shahafs@mellanox.com \
    --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).