From: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
To: Nidhia Varghese <nidhiavarghese93@gmail.com>,
"users@dpdk.org" <users@dpdk.org>, "dev@dpdk.org" <dev@dpdk.org>
Cc: raman geetha gopalakrishnan <glowingsun@gmail.com>,
"Singh, Jasvinder" <jasvinder.singh@intel.com>
Subject: Re: [dpdk-dev] Work with IP_PIPELINE application with non-supporting NIC
Date: Mon, 3 Apr 2017 10:13:06 +0000 [thread overview]
Message-ID: <3EB4FA525960D640B5BDFFD6A3D89126527855E3@IRSMSX108.ger.corp.intel.com> (raw)
In-Reply-To: <CAAx9ALXewsz3hnQHkWa2J83+cCkK_0G5odosRQc59YqAT2AmBQ@mail.gmail.com>
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Nidhia Varghese
> Sent: Monday, April 3, 2017 11:03 AM
> To: users@dpdk.org; dev@dpdk.org
> Subject: [dpdk-dev] Work with IP_PIPELINE application with non-supporting
> NIC
>
> Hi,
>
> Currently I am planning to develop a DPDK application using Packet
> Framework. But I do not have a DPDK supported NIC.
> I was able to run l2fwd application using AF_PACKET pmd. But when I tried
> to run ip pipeline application using "--vdev=af_packet0,iface=eno2
> --vdev=af_packet1,iface=eno3" I found that usage of --vdev argument is not
> supported for ip pipeline applications.
> In what way I can receive packets from a non-supporting NIC and give it to
> the pipeline for processing?
>
> Thank you so much for your reply and help.
>
> --
>
> Regards,
> Nidhia Varghese
Hi Nidhia,
The usage if --vdev is actually supported by ip_pipeline through the use of EAL section in config file:
[EAL]
vdev = <arguments to be passed to the EAL --vdev option>
Once this is done, the port and queues can be used through the LINK, RXQ and TXQ objects, like any other PMD port.
Regards,
Cristian
prev parent reply other threads:[~2017-04-03 10:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 10:03 Nidhia Varghese
2017-04-03 10:13 ` Dumitrescu, Cristian [this message]
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=3EB4FA525960D640B5BDFFD6A3D89126527855E3@IRSMSX108.ger.corp.intel.com \
--to=cristian.dumitrescu@intel.com \
--cc=dev@dpdk.org \
--cc=glowingsun@gmail.com \
--cc=jasvinder.singh@intel.com \
--cc=nidhiavarghese93@gmail.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).