From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Shyam Shrivastav <shrivastav.shyam@gmail.com>, users@dpdk.org
Subject: Re: [dpdk-users] Unable to bind intel NIC 82599ES to vfio-pci, uio_pci_generic
Date: Mon, 13 Feb 2017 17:01:36 +0000 [thread overview]
Message-ID: <d80e179d-a942-c961-edfa-e79a22c2e4ca@intel.com> (raw)
In-Reply-To: <CAGSp03m=+YPz-fkknCbhLSCNiDPTiqmG0_SgvvAV1TCXVVwnhw@mail.gmail.com>
On 2/8/2017 7:19 AM, Shyam Shrivastav wrote:
> Hi All
>
> I am not able to bind 82599 to either uio_pci_generic or vfio-pci
> successfully. Any help greatly appreciated, I am completely stuck at this
> initial step.
>
> *1) uio_pci_generic* : tools/dpdk-devbind.py script reports success but it
> is not detected by EAL on initialisation, still ixgbe driver is detected.
> here is relevant console output
It is detected, but according following log ports are not enabled by
proper application (not eal) command line argument:
" Cause: All available ports are disabled. Please set portmask."
./examples/l2fwd/build/l2fwd [EAL options] -- -p PORTMASK [-q NQ]
-p PORTMASK: hexadecimal bitmask of ports to configure
-q NQ: number of queue (=ports) per lcore (default is 1)
-T PERIOD: statistics will be refreshed each PERIOD seconds (0 to
disable, 10 default, 86400 maximum)
--[no-]mac-updating: Enable or disable MAC addresses updating (enabled
by default)
When enabled:
- The source MAC address is replaced by the TX port MAC address
- The destination MAC address is replaced by
02:00:00:00:00:TX_PORT_ID
<...>
>
>
>
> *2) vfio-pci :* Configured vfio permissions using setup.sh, bind script
> reports error in this case as under
Not sure about this one, below looks correct. Perhaps dmesg can tell more.
<...>
>
> Thanks
> Shyam
>
next prev parent reply other threads:[~2017-02-13 17:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 7:19 Shyam Shrivastav
2017-02-13 17:01 ` Ferruh Yigit [this message]
2017-02-14 5:34 ` Shyam Shrivastav
2017-02-08 12:47 Shyam Shrivastav
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=d80e179d-a942-c961-edfa-e79a22c2e4ca@intel.com \
--to=ferruh.yigit@intel.com \
--cc=shrivastav.shyam@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).