[dpdk-dev] [PATCH 1/2] Introduce if_index field to struct rte_eth_dev_info

2014-01-09 Thread Thomas Monjalon
09/01/2014 09:44, Mats Liljegren: > I'll prepare new patches. As you may know (and as described in http://dpdk.org/dev#send), you can use these options to send new versions of your patches: git send-email --subject-prefix 'PATCH v3' --annotate Thank you -- Thomas

[dpdk-dev] [PATCH 1/2] Introduce if_index field to struct rte_eth_dev_info

2014-01-09 Thread Mats Liljegren
On Thu, Jan 9, 2014 at 7:30 AM, Stephen Hemminger wrote: > Technically in Linux ifindex is unsigned 32 bit value. And 0 is > reserved as a marker. > Therefore why not use that semantic. > > On Wed, Jan 8, 2014 at 1:46 AM, Mats Liljegren > wrote: >> This field is intended for pcap to describe the

[dpdk-dev] [PATCH 1/2] Introduce if_index field to struct rte_eth_dev_info

2014-01-08 Thread Stephen Hemminger
Technically in Linux ifindex is unsigned 32 bit value. And 0 is reserved as a marker. Therefore why not use that semantic. On Wed, Jan 8, 2014 at 1:46 AM, Mats Liljegren wrote: > This field is intended for pcap to describe the name of the interface > as known to Linux. It is an interface index, b

[dpdk-dev] [PATCH 1/2] Introduce if_index field to struct rte_eth_dev_info

2014-01-08 Thread Mats Liljegren
This field is intended for pcap to describe the name of the interface as known to Linux. It is an interface index, but can be translated into an interface name using if_indextoname() function. When using pcap, interrupt affinity becomes important, and this field gives the application a chance to e