On Wed, 27 May 2026 at 16:44, Stephen Hemminger <[email protected]> wrote: > + * ``rte_eth_macaddrs_get``
I am not enthousiastic on marking this stable. It more or less sets in stone that the mac addresses are stored in an array. The initial goal was to retrieve all mac addresses of a port (21.11 release note entry): """ * **Added support to get all MAC addresses of a device.** Added ``rte_eth_macaddrs_get`` to allow a user to retrieve all Ethernet addresses assigned to a given Ethernet port. """ And this is how it is used in testpmd. https://git.dpdk.org/dpdk/tree/app/test-pmd/config.c#n7618 I'd rather see an API using an iterator that abstracts how macs are stored. That would also make it possible to skip null macs (which I find ugly in existing code). RTE_ETH_DEV_FOREACH_MAC(mac, port_id) { } -- David Marchand
