From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] l3fwd error, port 0 is not present on the board
Date: Tue, 6 Jan 2015 09:41:21 +0000 [thread overview]
Message-ID: <20150106094120.GA1488@bricha3-MOBL3> (raw)
In-Reply-To: <1613023.VipzgMKAkl@xps13>
On Tue, Jan 06, 2015 at 10:02:25AM +0100, Thomas Monjalon wrote:
> 2015-01-02 09:07, Lyn M:
> > In my original post, I thought my choice of hex portmask -p 0x3 was causing
> > this issue -- now I know that was not the case. But, I am still curious
> > about how the hex portmask is determined. Since I only have two ports
> > bound to igb_uio, my hex postmask will always be 0x3? What if I choose to
> > bind other ports to igb_uio? Is there a Linux command I can run to
> > determine what mask to use with the -p option?
>
> That's something which could be done.
> Port numbering is defined by probing order. Does a tool showing the (dry-run)
> probed devices, their number and mask, would help you?
> By the way, you are welcome to try developing it.
>
> --
> Thomas
The port numbering should generally be in the same order as the ports are listed
in dpdk_nic_bind script, so perhaps we could just add a documentation note to
that effect.
/Bruce
prev parent reply other threads:[~2015-01-06 9:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-29 20:18 Lyn M
2014-12-29 21:02 ` Neil Horman
2014-12-30 18:54 ` Lyn M
2014-12-30 21:24 ` Neil Horman
2014-12-31 14:18 ` Lyn M
2014-12-31 14:48 ` Neil Horman
2014-12-31 16:50 ` Lyn M
2015-01-01 3:37 ` Neil Horman
2015-01-01 4:00 ` Neil Horman
2015-01-02 15:07 ` Lyn M
2015-01-02 19:54 ` Neil Horman
2015-01-04 3:50 ` Qiu, Michael
2015-01-06 9:02 ` Thomas Monjalon
2015-01-06 9:41 ` Bruce Richardson [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=20150106094120.GA1488@bricha3-MOBL3 \
--to=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=thomas.monjalon@6wind.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).