I guess theres not much interest from others for this support in
general, but putting it out here in case anyone wants to take a look.
If anyone finds any major issues with the diffset, please do let me
know, that will be of great help. I have tested this on my machine.
Rgds,
Gopa.
--
This implementation is designed to provide a familar interface for applications
that rely on kernel-space driver to support ethtool_op and net_device_op for
device management. The initial implementation focuses on ops that can be
implemented through existing netdev APIs. More ops will be support
add two new apis: rte_eth_dev_default_mac_addr_set
and rte_eth_ethtool_dev_info to enable
reading device parameters (mac, register, eeprom,
pause, ring) based upon ethtool alike
data parameter sepcification.
Signed-off-by: Liang-Min Larry Wang
---
lib/librte_ether/Makefile | 1 +
add function to support ethtool ops:
- set_mac_addr
- get_reg_length
- get_regs
- get_eeprom_length
- get_eeprom
- set_eeprom
Signed-off-by: Liang-Min Larry Wang
---
drivers/net/ixgbe/ixgbe_ethdev.c | 178 +-
drivers/net/ixgbe/ixgbe_regs.h | 376
add function to support ethtool ops:
- set_mac_addr
- get_reg_length
- get_regs
- get_eeprom_length
- get_eeprom
- set_eeprom
Signed-off-by: Liang-Min Larry Wang
---
drivers/net/e1000/igb_ethdev.c | 175
drivers/net/e1000/igb_regs.h | 223 ++
The example includes an ethtool library and two applications:
one application is a non- DPDK process (nic-control)
and the other is a DPDK l2fwd applicaiton (l2fwd-app).
The nic-control process sends ethtool alike device management
requests to l2fwd-app through a named pipe IPC. This example
is des
> Change the order that user supplied RX and TX callbacks are called
> to the order that they were added (fifo).
>
> The previous calling order was the reverse of this (lifo) and was
> counter intuitive for users.
>
> Signed-off-by: John McNamara
Applied, thanks
7 matches
Mail list logo
