[dpdk-users] Not able to access /dev/uioX from inside LXC

2016-11-15 Thread Nagaprabhanjan Bellaru
There were two issues w.r.t the above problem

* The uioX major number is not fixed across machine reboots - so I had to
keep two-three major numbers in devices.allow section to do this.
* The sysfs was mounted as read-only file system. When I remounted it as
read-write, all problems went away. I could access 40G ports from inside
LXC container.

Thanks,
-nagp

On Sat, Nov 12, 2016 at 8:02 PM, Nagaprabhanjan Bellaru <
nagp.lists at gmail.com> wrote:

> Hi,
>
> The instructions mentioned by Krishnamurthy here:
> http://dpdk.org/ml/archives/dev/2014-October/006373.html
>
> greatly helped to make progress on accessing PCI devices from with in the
> container, however, DPDK is not able to open them because of privilege
> issues. Has somebody been able to crack this issue? If so, can they please
> show me the way to do it?
>
> --
> EAL: Detected 24 lcore(s)
> EAL: No free hugepages reported in hugepages-1048576kB
> EAL: Probing VFIO support...
> [New Thread 0x7fff8ece0700 (LWP 22134)]
> EAL: PCI device :06:00.0 on NUMA socket -1
> EAL:   probe driver: 8086:1583 rte_i40e_pmd
> EAL: Cannot open /dev/uio0: Operation not permitted
> EAL: Error - exiting with code: 1
>   Cause: Requested device :06:00.0 cannot be used
> [Thread 0x77fe7700 (LWP 22130) exited]
> [Inferior 1 (process 22130) exited with code 01]
> --
>
> Thanks,
> -nagp
>


[dpdk-users] DELOCK QSFP cables supported?

2016-11-14 Thread Nagaprabhanjan Bellaru
I have Intel XL710 Cards on my server. When I try to bring them up,
"rte_eth_dev_start" is returning "-95" (not supported). When I probed
through GDB, I found that i40e driver is returning "I40E_ERR_UNKNOWN_PHY"
for the plugged in cable.

Does anybody know whether this is supported or not?

Thanks,
-nagp


[dpdk-users] Not able to access /dev/uioX from inside LXC

2016-11-12 Thread Nagaprabhanjan Bellaru
Hi,

The instructions mentioned by Krishnamurthy here:
http://dpdk.org/ml/archives/dev/2014-October/006373.html

greatly helped to make progress on accessing PCI devices from with in the
container, however, DPDK is not able to open them because of privilege
issues. Has somebody been able to crack this issue? If so, can they please
show me the way to do it?

--
EAL: Detected 24 lcore(s)
EAL: No free hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
[New Thread 0x7fff8ece0700 (LWP 22134)]
EAL: PCI device :06:00.0 on NUMA socket -1
EAL:   probe driver: 8086:1583 rte_i40e_pmd
EAL: Cannot open /dev/uio0: Operation not permitted
EAL: Error - exiting with code: 1
  Cause: Requested device :06:00.0 cannot be used
[Thread 0x77fe7700 (LWP 22130) exited]
[Inferior 1 (process 22130) exited with code 01]
--

Thanks,
-nagp


[dpdk-users] Compiling DPDK 16.07 with shared option is failing..

2016-11-10 Thread Nagaprabhanjan Bellaru
I am not sure why it complains about "rte_eth_bond_8023ad_conf_get at DPDK_2.0"
when I cam compiling for 16.07. Anyways, if I change the symbol names, the
compilation goes through fine.

-nagp

On Thu, Nov 10, 2016 at 1:53 PM, Nagaprabhanjan Bellaru <
nagp.lists at gmail.com> wrote:

> Hi,
>
> I am compiling DPDK as part of VPP (Cisco). It has rte_timer etc. turned
> off. I enabled it and stumbled on this error. DPDK compilation is invoked
> by VPP.
>
> -nagp
>
> On Thu, Nov 10, 2016 at 1:48 PM, Thomas Monjalon <
> thomas.monjalon at 6wind.com> wrote:
>
>> 2016-11-10 10:37, Nagaprabhanjan Bellaru:
>> >  I found that librte_timer was not enabled and so the compilation
>> failed.
>> > When I enabled the same, it went ahead and failed at a different place
>> > while compiling librte_pmd:
>> >
>> > --
>> > gcc -pie -fPIC
>> > -L/home/ubuntu/development/libfwdd/src/platform/vpp/vpp/buil
>> d-root/install-vpp_debug-native/dpdk/lib
>> > -Wl,-g -shared rte_eth_bond_api.o rte_eth_bond_pmd.o rte_eth_bond_args.o
>> > rte_eth_bond_8023ad.o rte_eth_bond_alb.o -z defs -lrte_mbuf -lethdev
>> > -lrte_eal -lrte_kvargs -lrte_cmdline -lrte_mempool -lrte_ring
>> > -Wl,-soname,librte_pmd_bond.so.1.1 -o librte_pmd_bond.so.1.1
>> > /usr/bin/ld: librte_pmd_bond.so.1.1: version node not found for symbol
>> > rte_eth_bond_8023ad_conf_get at DPDK_2.0
>> > /usr/bin/ld: failed to set dynamic section sizes: Bad value
>> > collect2: error: ld returned 1 exit status
>> > --
>>
>> What are you changing in the default configuration?
>> Which commands are you using to compile?
>>
>
>


[dpdk-users] Compiling DPDK 16.07 with shared option is failing..

2016-11-10 Thread Nagaprabhanjan Bellaru
Hi,

I am compiling DPDK as part of VPP (Cisco). It has rte_timer etc. turned
off. I enabled it and stumbled on this error. DPDK compilation is invoked
by VPP.

-nagp

On Thu, Nov 10, 2016 at 1:48 PM, Thomas Monjalon 
wrote:

> 2016-11-10 10:37, Nagaprabhanjan Bellaru:
> >  I found that librte_timer was not enabled and so the compilation failed.
> > When I enabled the same, it went ahead and failed at a different place
> > while compiling librte_pmd:
> >
> > --
> > gcc -pie -fPIC
> > -L/home/ubuntu/development/libfwdd/src/platform/vpp/vpp/
> build-root/install-vpp_debug-native/dpdk/lib
> > -Wl,-g -shared rte_eth_bond_api.o rte_eth_bond_pmd.o rte_eth_bond_args.o
> > rte_eth_bond_8023ad.o rte_eth_bond_alb.o -z defs -lrte_mbuf -lethdev
> > -lrte_eal -lrte_kvargs -lrte_cmdline -lrte_mempool -lrte_ring
> > -Wl,-soname,librte_pmd_bond.so.1.1 -o librte_pmd_bond.so.1.1
> > /usr/bin/ld: librte_pmd_bond.so.1.1: version node not found for symbol
> > rte_eth_bond_8023ad_conf_get at DPDK_2.0
> > /usr/bin/ld: failed to set dynamic section sizes: Bad value
> > collect2: error: ld returned 1 exit status
> > --
>
> What are you changing in the default configuration?
> Which commands are you using to compile?
>


[dpdk-users] Compiling DPDK 16.07 with shared option is failing..

2016-11-10 Thread Nagaprabhanjan Bellaru
 I found that librte_timer was not enabled and so the compilation failed.
When I enabled the same, it went ahead and failed at a different place
while compiling librte_pmd:

--
gcc -pie -fPIC
-L/home/ubuntu/development/libfwdd/src/platform/vpp/vpp/build-root/install-vpp_debug-native/dpdk/lib
-Wl,-g -shared rte_eth_bond_api.o rte_eth_bond_pmd.o rte_eth_bond_args.o
rte_eth_bond_8023ad.o rte_eth_bond_alb.o -z defs -lrte_mbuf -lethdev
-lrte_eal -lrte_kvargs -lrte_cmdline -lrte_mempool -lrte_ring
-Wl,-soname,librte_pmd_bond.so.1.1 -o librte_pmd_bond.so.1.1
/usr/bin/ld: librte_pmd_bond.so.1.1: version node not found for symbol
rte_eth_bond_8023ad_conf_get at DPDK_2.0
/usr/bin/ld: failed to set dynamic section sizes: Bad value
collect2: error: ld returned 1 exit status
--

I see that the symbol is present in drivers/net/bonding, but I am not sure
how to fix this error. Can someone please help me?

Thanks,
-nagp

On Wed, Nov 9, 2016 at 6:04 PM, Nagaprabhanjan Bellaru  wrote:

> Hi,
>
> I am compiling DPDK with "CONFIG_RTE_BUILD_SHARED_LIB=y". However, when I
> compile, it is failing at:
>
> --
> gcc -pie -fPIC -L/home/ubuntu/development/libfwdd/src/platform/vpp/vpp/
> build-root/install-vpp_debug-native/dpdk/lib  -Wl,-g -shared rte_sched.o
> rte_red.o rte_approx.o rte_reciprocal.o -z defs -lm -lrt -lrte_eal
> -lrte_mempool -lrte_mbuf -lrte_timer -Wl,-soname,librte_sched.so.1.1 -o
> librte_sched.so.1.1
> /usr/bin/ld: cannot find -lrte_timer
> --
>
> I can see that librte_timer is not compiled yet, however librte_sched
> depends on it - is there any workaround for this issue? Can I change the
> order somewhere?
>
> Thanks,
> -nagp
>


[dpdk-users] Compiling DPDK 16.07 with shared option is failing..

2016-11-09 Thread Nagaprabhanjan Bellaru
Hi,

I am compiling DPDK with "CONFIG_RTE_BUILD_SHARED_LIB=y". However, when I
compile, it is failing at:

--
gcc -pie -fPIC
-L/home/ubuntu/development/libfwdd/src/platform/vpp/vpp/build-root/install-vpp_debug-native/dpdk/lib
-Wl,-g -shared rte_sched.o rte_red.o rte_approx.o rte_reciprocal.o -z defs
-lm -lrt -lrte_eal -lrte_mempool -lrte_mbuf -lrte_timer
-Wl,-soname,librte_sched.so.1.1 -o librte_sched.so.1.1
/usr/bin/ld: cannot find -lrte_timer
--

I can see that librte_timer is not compiled yet, however librte_sched
depends on it - is there any workaround for this issue? Can I change the
order somewhere?

Thanks,
-nagp


[dpdk-users] Not able to access uio0/device/config from LXC

2016-03-10 Thread Nagaprabhanjan Bellaru
I have followed the steps mentioned in this thread:


to create a uio0, but EAL complains about the following:
--
EAL: Cannot open /sys/class/uio/uio0/device/config: Permission denied
EAL: Error - exiting with code: 1
  Cause: Requested device :00:19.0 cannot be used
--

even though I run as a root user and have all the rw permissions. Can
anybody tell me what else I could be missing?

Thanks,
-nagp


[dpdk-users] Not able to detect Intel EC I218-V (rev 03)

2016-02-26 Thread Nagaprabhanjan Bellaru
Hello,

Using setup.sh (available in tools folder) I have bound eth0 (which is of
Intel EC I218-V make) to igb_uio module (which I can see with
dpdk_nic_bind.py --status output):

--
Network devices using DPDK-compatible driver

:00:19.0 'Ethernet Connection (3) I218-V' drv=igb_uio unused=

Network devices using kernel driver
===

--

However, when I run any sample application, it complains that there are no
ethernet ports:

--
EAL: Error - exiting with code: 1
  Cause: No available NIC ports!
--

If I give a --vdev=eth_pcap0,iface=eth0, then it picks it. Am I missing
something? I hope this Intel card is supported by DPDK.

Thanks,
-nagp