[dpdk-dev] [PATCH RFC 0/3] only call iopl when necessary

2014-09-29 Thread Thomas Monjalon
2014-08-26 16:11, David Marchand: > This patch series is just a little clean up to remove the unconditionnal call > to > iopl on linux. > Rather than call iopl() at the eal level, let the PMD that needs it call > rte_eal_iopl_init(). Acked and applied Thanks for the cleanup -- Thomas

[dpdk-dev] [PATCH RFC 0/3] only call iopl when necessary

2014-08-27 Thread Patel, Rashmin N
> -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of David Marchand > Sent: Tuesday, August 26, 2014 10:12 PM > To: dev at dpdk.org > Subject: [dpdk-dev] [PATCH RFC 0/3] only call iopl when necessary > > This patch series is just a little c

[dpdk-dev] [PATCH RFC 0/3] only call iopl when necessary

2014-08-27 Thread Stephen Hemminger
Yes. Iopl is to allow out from user space. I played with ioperm instead but that is per thread and was a nuisance.

[dpdk-dev] [PATCH RFC 0/3] only call iopl when necessary

2014-08-27 Thread Thomas Monjalon
om] > Sent: Wednesday, August 27, 2014 6:05 PM > To: Xie, Huawei > Cc: dev at dpdk.org > Subject: Re: [dpdk-dev] [PATCH RFC 0/3] only call iopl when necessary > > > On Wed, Aug 27, 2014 at 11:57 AM, Xie, Huawei intel.com<mailto:huawei.xie at intel.com>> wrote:

[dpdk-dev] [PATCH RFC 0/3] only call iopl when necessary

2014-08-27 Thread David Marchand
On Wed, Aug 27, 2014 at 11:57 AM, Xie, Huawei wrote: > That is ok. If virtio PMD is a dynamic linked library, is it possible > that virtio PMD is loaded later? > The shared library are loaded through -d option, which are loaded just before the call to rte_eal_dev_init(). -- David Marchand >

[dpdk-dev] [PATCH RFC 0/3] only call iopl when necessary

2014-08-27 Thread David Marchand
Hello, On Wed, Aug 27, 2014 at 11:22 AM, Xie, Huawei wrote: > Hi David: > The reason iopl is put in rte_eal_init is that we want all later created > DPDK processes/threads inherit the iopl permission. > If you only call iopl in pmd_init, RX/TX and other threads which needs io > permission will s

[dpdk-dev] [PATCH RFC 0/3] only call iopl when necessary

2014-08-27 Thread Xie, Huawei
-dev] [PATCH RFC 0/3] only call iopl when necessary On Wed, Aug 27, 2014 at 11:57 AM, Xie, Huawei mailto:huawei.xie at intel.com>> wrote: That is ok. If virtio PMD is a dynamic linked library, is it possible that virtio PMD is loaded later? The shared library are loaded through -d option, whi

[dpdk-dev] [PATCH RFC 0/3] only call iopl when necessary

2014-08-27 Thread Xie, Huawei
That is ok. If virtio PMD is a dynamic linked library, is it possible that virtio PMD is loaded later? From: David Marchand [mailto:david.march...@6wind.com] Sent: Wednesday, August 27, 2014 5:34 PM To: Xie, Huawei Cc: dev at dpdk.org Subject: Re: [dpdk-dev] [PATCH RFC 0/3] only call iopl when

[dpdk-dev] [PATCH RFC 0/3] only call iopl when necessary

2014-08-27 Thread Xie, Huawei
m: dev [mailto:dev-bounces at dpdk.org] On Behalf Of David Marchand > Sent: Tuesday, August 26, 2014 10:12 PM > To: dev at dpdk.org > Subject: [dpdk-dev] [PATCH RFC 0/3] only call iopl when necessary > > This patch series is just a little clean up to remove the unconditionnal call

[dpdk-dev] [PATCH RFC 0/3] only call iopl when necessary

2014-08-26 Thread David Marchand
This patch series is just a little clean up to remove the unconditionnal call to iopl on linux. Rather than call iopl() at the eal level, let the PMD that needs it call rte_eal_iopl_init(). -- David Marchand David Marchand (3): eal/bsd: fix fd leak eal: don't call rte_eal_iopl_init unconditi