DPDK usage discussions
 help / color / mirror / Atom feed
From: "Lukáš Šišmiš" <sismis@cesnet.cz>
To: users@dpdk.org
Cc: cristian.dumitrescu@intel.com
Subject: Initialize SoftNIC to work with rte_flow rules
Date: Fri, 22 Sep 2023 10:35:38 +0200	[thread overview]
Message-ID: <a266d8f0-1d35-9f4d-aa46-b63fea697a80@cesnet.cz> (raw)

Hi all,


I am trying to setup completely virtual development environment where it 
would be possible to develop applications with rte_flow rules.

For this, I've found SoftNIC as a viable solution as this is supposed to 
be a software NIC that also supports rte_flow rules.

However, I am having a hard time to set it up, I couldn't find good 
examples/documentation for this. Examples/docs found in 
ip_pipeline/pipeline examples are outdated.

I was able to make it run through testpmd but without the support for 
rte_flow.

Could you please help me to create spec/cli file that would support this 
use case?


I am currently primarily interested in RX direction although being able 
to work in the TX direction would be greatly appreciated.

The solution I am currently thinking of:

net_pcap0 -> net_softnic0 -> DPDK application + TX( -> net_softnic0 -> 
net_ring/net_null)


The RX path can be done - and I was able to run it in testpmd but then 
testpmd complained when I tried to apply rte_flow rules (not 
implemented). Makes sense considering that the softnic default pipeline 
doesn't contain any tables I guess.


Thank you all in advance.

I'm CC'ing Cristian as he is the SoftNIC maintainer.


Cheers,

Lukas Sismis



             reply	other threads:[~2023-09-22  8:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-22  8:35 Lukáš Šišmiš [this message]
2023-09-29  9:55 ` Dumitrescu, Cristian
2023-09-29 11:21   ` Lukáš Šišmiš

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=a266d8f0-1d35-9f4d-aa46-b63fea697a80@cesnet.cz \
    --to=sismis@cesnet.cz \
    --cc=cristian.dumitrescu@intel.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).