[dpdk-dev] [PATCH] doc: remove iomem and ioport handling in igb_uio

2016-11-13 Thread Thomas Monjalon
> > Suggested-by: Yigit, Ferruh > > Signed-off-by: Jianfeng Tan > > Acked-by: Remy Horton Applied

[dpdk-dev] [PATCH] doc: remove iomem and ioport handling in igb_uio

2016-11-11 Thread Remy Horton
On 22/09/2016 13:44, Jianfeng Tan wrote: [..] > > Suggested-by: Yigit, Ferruh > Signed-off-by: Jianfeng Tan Acked-by: Remy Horton > +++ b/doc/guides/rel_notes/deprecation.rst > @@ -57,3 +57,8 @@ Deprecation Notices > * API will change for ``rte_port_source_params`` and ``rte_port_sink_param

[dpdk-dev] [PATCH] doc: remove iomem and ioport handling in igb_uio

2016-09-30 Thread Ferruh Yigit
On 9/22/2016 6:44 AM, Jianfeng Tan wrote: > 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

[dpdk-dev] [PATCH] doc: remove iomem and ioport handling in igb_uio

2016-09-22 Thread Jianfeng Tan
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/de