From: Rami Rosen <roszenrami@gmail.com>
To: Kushal Gautam <kushal.gautam@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] using the basic l2fwd app
Date: Thu, 18 Oct 2018 20:34:45 +0300 [thread overview]
Message-ID: <CAKoUAr=Pp6RnxzzAfyKD4ADOH90ZoKP9FtWgx7-P=pcwvkfbhg@mail.gmail.com> (raw)
In-Reply-To: <CAGv3bDefPk1ifeoh42-Fzf5K2OkAwRWx7fHx=VSpgQAZ86RS=A@mail.gmail.com>
Hi Kushal,
The output of dpdk-devbind -- status that you posted shows that there are
no ports that are bound to dpdk. This is the reason for the error you get.
You should try
insmod igb_uio.ko
( this kernel module is generated in the build process of DPDK)
And
dpdk-devbind.py -b igb_uio 0000:81:00.0
And likewise to the other port, 0000:81:00.1
And the launch the l2fwd app.
You can also use vfio-pci or uio_pci_generic for binding the device to
DPDK, look in the docs.
Regards,
Rami Rosen
בתאריך יום ה׳, 18 באוק׳ 2018, 17:24, מאת Kushal Gautam <
kushal.gautam@gmail.com>:
> Hi:
>
> I am new to DPDK and my current use case with DPDK is minimal. Thus, I
> think the l2fwd type of sample application should suffice.
>
> Below is a portion of the output of `dpdk-devbind.py --status` command
> My DPDK version is 18.08, and I am using Ubuntu 16.04 (Linux Kernel version
> 4.15.12)
>
> Network devices using kernel driver
> ===================================
> 0000:01:00.0 'I350 Gigabit Network Connection 1521' if=eno1 drv=igb
> unused=igb_uio *Active*
> 0000:01:00.1 'I350 Gigabit Network Connection 1521' if=eno2 drv=igb
> unused=igb_uio
> 0000:81:00.0 'Ethernet Controller X710 for 10GbE SFP+ 1572' if=ens1f0
> drv=i40e unused=igb_uio *Active*
> 0000:81:00.1 'Ethernet Controller X710 for 10GbE SFP+ 1572' if=ens1f1
> drv=i40e unused=igb_uio *Active*
>
> I am connecting to this machine via 0000:01:00.0
>
> My requirement is to be able to send packets from 0000:81:00.0 to
> 0000:81:00.1 and get some measurements like tx and rx times.
>
> I tried to run the sample app as (as shown in docs):
>
> ./l2fwd -n 1 -c f -- -q 8 -p 0x3
>
> I have an error like this:
>
> EAL: Detected 16 lcore(s)
> EAL: Detected 2 NUMA nodes
> EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
> EAL: No free hugepages reported in hugepages-1048576kB
> EAL: No free hugepages reported in hugepages-1048576kB
> EAL: No free hugepages reported in hugepages-1048576kB
> EAL: Probing VFIO support...
> EAL: PCI device 0000:01:00.0 on NUMA socket 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:01:00.1 on NUMA socket 0
> EAL: probe driver: 8086:1521 net_e1000_igb
> EAL: PCI device 0000:81:00.0 on NUMA socket 1
> EAL: probe driver: 8086:1572 net_i40e
> EAL: PCI device 0000:81:00.1 on NUMA socket 1
> EAL: probe driver: 8086:1572 net_i40e
> MAC updating enabled
> EAL: Error - exiting with code: 1
> Cause: No Ethernet ports - bye
>
> I did not understand the usage of port mask in this context.
>
> Some inputs on this would be very helpful.
>
> Regards,
> Kushal.
>
next prev parent reply other threads:[~2018-10-18 17:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 14:24 Kushal Gautam
2018-10-18 17:34 ` Rami Rosen [this message]
2018-10-18 21:17 ` Kushal Gautam
2018-10-18 23:36 ` Rami Rosen
2018-10-19 6:54 ` Kushal Gautam
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='CAKoUAr=Pp6RnxzzAfyKD4ADOH90ZoKP9FtWgx7-P=pcwvkfbhg@mail.gmail.com' \
--to=roszenrami@gmail.com \
--cc=kushal.gautam@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).