doc: announce iomem and ioport removal from igb_uio
In igb_uio, iomem is mapped, and both ioport and io mem are recorded into uio framework (then into sysfs files), which is duplicated with what Linux has already provided for user space, and makes the code too complex. For iomem, DPDK user space code never opens or reads files under /sys/pci/bus/devices/xxxx:xx:xx.x/uio/uioY/maps/. Instead, /sys/pci/bus/devices/xxxx:xx:xx.x/resourceY are used to map device memory. For ioport, non-x86 platforms cannot read from files under /sys/pci/bus/devices/xxxx:xx:xx.x/uio/uioY/portio/ directly, because non-x86 platforms need to map port region for access in user space, see non-x86 version pci_uio_ioport_map(). x86 platforms can use the the same way as uio_pci_generic. This will remove iomem and ioport mapping in igb_uio kernel module, and adjusts the iomem implementation in both igb_uio and uio_pci_generic: - for x86 platform, get ports info from /proc/ioports; - for non-x86 platform, map and get ports info by pci_uio_ioport_map(). Note: this will affect those applications who are using files under /sys/pci/bus/devices/xxxx:xx:xx.x/uio/uioY/maps/ and /sys/pci/bus/devices/xxxx:xx:xx.x/uio/uioY/portio/. Suggested-by: Ferruh Yigit <ferruh.yigit@intel.com> Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com> Acked-by: Ferruh Yigit <ferruh.yigit@intel.com> Acked-by: Remy Horton <remy.horton@intel.com>
This commit is contained in:
parent
6be532b929
commit
3bac1dbc1e
@ -8,6 +8,11 @@ API and ABI deprecation notices are to be posted here.
|
||||
Deprecation Notices
|
||||
-------------------
|
||||
|
||||
* igb_uio: iomem mapping and sysfs files created for iomem and ioport in
|
||||
igb_uio will be removed, because we are able to detect these from what Linux
|
||||
has exposed, like the way we have done with uio-pci-generic. This change
|
||||
targets release 17.02.
|
||||
|
||||
* In 17.02 ABI changes are planned: the ``rte_eth_dev`` structure will be
|
||||
extended with new function pointer ``tx_pkt_prepare`` allowing verification
|
||||
and processing of packet burst to meet HW specific requirements before
|
||||
|
Loading…
Reference in New Issue
Block a user