>-----Original Message----- >From: Thomas Monjalon [mailto:tho...@monjalon.net] >Sent: 5. januar 2018 13:02 >To: Finn Christensen <f...@napatech.com> >Cc: dev@dpdk.org; Yuanhan Liu <y...@fridaylinux.org>; Adrien Mazarguil ><adrien.mazarg...@6wind.com>; Ciara Loftus <ciara.lof...@intel.com>; Kevin >Traynor <ktray...@redhat.com>; step...@networkplumber.org; >ferruh.yi...@intel.com >Subject: Re: [dpdk-dev] standardize device identification > >05/01/2018 12:09, Finn Christensen: >> From: Thomas Monjalon >> Which property can help to distinguish Napatech ports? >> Can you use class=eth,dev_port=X ? >> The dev_port property will use /sys/class/net/DEV/dev_port on Linux. Is >> it >> OK for you? >> >> Actually, what we were thinking of was using the mac property in the >> class category to distinguish our ports. >> For instance: >> -w bus=pci,id=0000:01:00.0/class=eth,mac=00:11:22:33:44:55 >> or simply: >> -w class=eth,mac=00:11:22:33:44:55 > >The problem with the mac property is that it cannot be used for >white/blacklisting in DPDK because the MAC is not known before port >initialization. >
Sure, that makes sense. I just for a minute thought that we could use that mechanism to enable individual ports at startup also. We will continue to use proprietary devargs passed by whiterlist to the PMD probe function. What we needed was a way to select the individual ports, by using rte_eth_dev_get_port_by_name(). >> We will not be able to support the dev_port property, that will not work for >us. >> At least not for now.
