From: "Xia, Chenbo" <chenbo.xia@intel.com>
To: Utkarsh Kathuria <utkarshkathuria22@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] How to use --vdev parameter?
Date: Wed, 28 Jul 2021 06:57:58 +0000 [thread overview]
Message-ID: <MN2PR11MB4063AE2CB18BD1461F82D5239CEA9@MN2PR11MB4063.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAHwUPr61tsBjr3LtuQ+rEKuc2ycnpy1NuDePcOhLkQC+Ay9j5A@mail.gmail.com>
Hi,
I am not very familiar with the github project you listed. But IIUC, the vdev param should be ‘--vdev=net_pcap0,iface=eno1’ and eno1 should
be the Intel 100G E810 NIC port.
/Chenbo
From: Utkarsh Kathuria <utkarshkathuria22@gmail.com>
Sent: Wednesday, July 28, 2021 2:49 PM
To: Xia, Chenbo <chenbo.xia@intel.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] How to use --vdev parameter?
Thank you so much for replying.
Actually I want to read the packets as per given in this link "https://github.com/ntop/nDPI/tree/dev/example". You can scroll down and see the command "./build/ndpiReader -c 1 --vdev=net_pcap0,iface=eno1 -- -v 1". Here they use --vdev=net_pcap0. I want to read the packets on my port of NIC. I know the above command uses dpdk parameters. So should I not put --vdev or how the above command is supposed to be written?
Please help
Regards
Utkarsh
On Wed, 28 Jul 2021 at 14:36, Xia, Chenbo <chenbo.xia@intel.com<mailto:chenbo.xia@intel.com>> wrote:
Hi Utkarsh,
> -----Original Message-----
> From: users <users-bounces@dpdk.org<mailto:users-bounces@dpdk.org>> On Behalf Of Utkarsh Kathuria
> Sent: Monday, July 26, 2021 5:48 PM
> To: users@dpdk.org<mailto:users@dpdk.org>
> Subject: [dpdk-users] How to use --vdev parameter?
>
> Hi,
> I am using Intel 100G E810 NIC card.
> I want to know that does the parameter --vdev=' ' values depend on what
> type of NIC card we use or not.
> For example: --vdev 'net_pcap0,rx_pcap=input.pcap,tx_pcap=output.pcap' in
> this statement why net_pcap0 was used?
> Please someone help me understand this.
Vdev param is for virtual devices and you are using real hardware devices.
So you don't need to consider this if you only want to start up the E810 NIC.
Thanks,
Chenbo
>
> Thank you
> Regards
> Utkarsh
prev parent reply other threads:[~2021-07-28 6:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-26 9:47 Utkarsh Kathuria
2021-07-28 6:36 ` Xia, Chenbo
2021-07-28 6:48 ` Utkarsh Kathuria
2021-07-28 6:57 ` Xia, Chenbo [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=MN2PR11MB4063AE2CB18BD1461F82D5239CEA9@MN2PR11MB4063.namprd11.prod.outlook.com \
--to=chenbo.xia@intel.com \
--cc=users@dpdk.org \
--cc=utkarshkathuria22@gmail.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).