I guess any Ethernet interface can be configured to work in loopback mode ( at least with SDK provided tools/functions). "Loopback" interface applied to HW is confusing - usually loopback is software only; how a HW packet classifier would be tested with a "loopback" interface? For this purpose a real interface is required, backed up by real HW.
On 25 November 2014 at 14:05, Taras Kondratiuk <[email protected]> wrote: > On 11/24/2014 08:27 PM, Maxim Uvarov wrote: > >> Hello, >> >> Can we go odp_pktio_open() return default interface provided by >> implementation? >> >> For linux-generic we already have environment variables to select >> between mmap and raw sockets. >> Also we can add hint what is default interface name. >> >> Like: >> export ODP_PKIO_DEFAULT_DEV="eth0" >> >> And if this variable is not exported it might be eth0, eth1, then eth2. >> Or first device found in list returned by ioctl. >> >> Reason is to add to CUNIT tests coverage for functions which need pktio. >> > > It makes more sense to have an API to request available pktio interfaces > and their characteristics. So application can pick one of them instead > of default. > > But as Bala mentioned for tests you need loopback interface, but not a > real one. > > > _______________________________________________ > lng-odp mailing list > [email protected] > http://lists.linaro.org/mailman/listinfo/lng-odp >
_______________________________________________ lng-odp mailing list [email protected] http://lists.linaro.org/mailman/listinfo/lng-odp
