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
