2015-06-02 15:47, Wang, Liang-min: > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > > >>I'm curious to understand how renaming rte_eth_dev_set_mtu() to > > >>rte_ethtool_net_change_mtu() will help anyone. > >> > >> As described, this interface is designed to provide API closely to kernel > >> space ethtool ops and net_device_op. > > >But the application still needs to adapt the code to call rte_* functions. > >So changing to rte_ethtool_net_change_mtu is equivalent to change to the > >existing rte_eth_dev_set_mtu. I don't see the benefit. > > The benefit is single interface for users to access. Instead of looking into > two different interfaces (ethtool, ether).
Sorry it doesn't help to understand. Today, there is an ethdev API. Why adding an ethtool-like API would help?
