Re: [dpdk-dev] [RFC] igb_uio: deprecate iomem and ioport mapping

2017-01-05 Thread Tan, Jianfeng
Hi, > -Original Message- > From: Yigit, Ferruh > Sent: Thursday, January 5, 2017 11:24 PM > To: Tan, Jianfeng; Stephen Hemminger > Cc: dev@dpdk.org; david.march...@6wind.com > Subject: Re: [RFC] igb_uio: deprecate iomem and ioport mapping > > On 12/5/2016 7:04 AM, Tan, Jianfeng wrote: > >

Re: [dpdk-dev] [RFC] igb_uio: deprecate iomem and ioport mapping

2017-01-05 Thread Ferruh Yigit
On 12/5/2016 7:04 AM, Tan, Jianfeng wrote: > Hi Stephen, > >> -Original Message- >> From: Stephen Hemminger [mailto:step...@networkplumber.org] >> Sent: Saturday, December 3, 2016 7:47 AM >> To: Tan, Jianfeng >> Cc: dev@dpdk.org; david.march...@6wind.com; Yigit, Ferruh >> Subject: Re: [RFC

Re: [dpdk-dev] [RFC] igb_uio: deprecate iomem and ioport mapping

2016-12-04 Thread Tan, Jianfeng
Hi Stephen, > -Original Message- > From: Stephen Hemminger [mailto:step...@networkplumber.org] > Sent: Saturday, December 3, 2016 7:47 AM > To: Tan, Jianfeng > Cc: dev@dpdk.org; david.march...@6wind.com; Yigit, Ferruh > Subject: Re: [RFC] igb_uio: deprecate iomem and ioport mapping > > On

Re: [dpdk-dev] [RFC] igb_uio: deprecate iomem and ioport mapping

2016-12-02 Thread Stephen Hemminger
On Thu, 1 Sep 2016 02:16:37 + Jianfeng Tan wrote: > Previously in igb_uio, iomem is mapped, and both ioport and io mem > are recorded into uio framework, which is duplicated and makes the > code too complex. > > For iomem, DPDK user space code never opens or reads files under > /sys/pci/bus

[dpdk-dev] [RFC] igb_uio: deprecate iomem and ioport mapping

2016-09-09 Thread Tan, Jianfeng
Hi David, Thank you for reviewing this. On 9/9/2016 5:06 PM, David Marchand wrote: > Hello Jianfeng, > > On Thu, Sep 1, 2016 at 4:16 AM, Jianfeng Tan > wrote: >> Previously in igb_uio, iomem is mapped, and both ioport and io mem >> are recorded into uio framework, which is duplicated and makes

[dpdk-dev] [RFC] igb_uio: deprecate iomem and ioport mapping

2016-09-09 Thread David Marchand
Hello Jianfeng, On Thu, Sep 1, 2016 at 4:16 AM, Jianfeng Tan wrote: > Previously in igb_uio, iomem is mapped, and both ioport and io mem > are recorded into uio framework, which is duplicated and makes the > code too complex. > > For iomem, DPDK user space code never opens or reads files under >

[dpdk-dev] [RFC] igb_uio: deprecate iomem and ioport mapping

2016-09-02 Thread Tan, Jianfeng
On 9/2/2016 8:31 PM, Ferruh Yigit wrote: > On 9/1/2016 3:16 AM, Jianfeng Tan wrote: >> Previously in igb_uio, iomem is mapped, and both ioport and io mem >> are recorded into uio framework, which is duplicated and makes the >> code too complex. >> >> For iomem, DPDK user space code never opens or

[dpdk-dev] [RFC] igb_uio: deprecate iomem and ioport mapping

2016-09-02 Thread Ferruh Yigit
On 9/1/2016 3:16 AM, Jianfeng Tan wrote: > Previously in igb_uio, iomem is mapped, and both ioport and io mem > are recorded into uio framework, which is duplicated and makes the > code too complex. > > For iomem, DPDK user space code never opens or reads files under > /sys/pci/bus/devices/:xx

[dpdk-dev] [RFC] igb_uio: deprecate iomem and ioport mapping

2016-09-01 Thread Jianfeng Tan
Previously in igb_uio, iomem is mapped, and both ioport and io mem are recorded into uio framework, which is duplicated and makes the code too complex. For iomem, DPDK user space code never opens or reads files under /sys/pci/bus/devices/:xx:xx.x/uio/uioY/maps/. Instead, /sys/pci/bus/devices/x