DPDK patches and discussions
 help / color / mirror / Atom feed
* [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
@ 2014-12-24 13:26 sothy shan
  2014-12-24 15:03 ` Masaru Oki
  2014-12-24 15:04 ` Neil Horman
  0 siblings, 2 replies; 14+ messages in thread
From: sothy shan @ 2014-12-24 13:26 UTC (permalink / raw)
  To: dev

Hello!

I am playing with DPDK 1.7.1 in Fedora.

When I do like this:

export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
make install T="$RTE_TARGET"

It worked. Means Testpmd is running.

When I run as mentioned below:

make CONFIG_RTE_BUILD_SHARED_LIB=y  install T="$RTE_TARGET"

Build is sucess. But Testpmd gives error.

Error is :

sudo ./x86_64-ivshmem-linuxapp-gcc/app/testpmd -c7 -n3 -- -i
--nb-cores=2 --nb-ports=2
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 0 on socket 0
EAL: Detected lcore 5 as core 1 on socket 0
EAL: Detected lcore 6 as core 2 on socket 0
EAL: Detected lcore 7 as core 3 on socket 0
EAL: Support maximum 64 logical core(s) by configuration.
EAL: Detected 8 lcore(s)
EAL: Searching for IVSHMEM devices...
EAL: No IVSHMEM configuration found!
EAL: Setting up memory...
EAL: Ask a virtual area of 0x1c00000 bytes
EAL: Virtual area found at 0x7f4329000000 (size = 0x1c00000)
EAL: Ask a virtual area of 0x5c00000 bytes
EAL: Virtual area found at 0x7f4323200000 (size = 0x5c00000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f432b600000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f432b200000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f432ae00000 (size = 0x200000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7f4322e00000 (size = 0x200000)
EAL: Requesting 64 pages of size 2MB from socket 0
EAL: TSC frequency is ~3691107 KHz
EAL: Master core 0 is ready (tid=5053c840)
EAL: Core 2 is ready (tid=21dfd700)
EAL: Core 1 is ready (tid=225fe700)
EAL: Error - exiting with code: 1
  Cause: No probed ethernet devices - check that
CONFIG_RTE_LIBRTE_IGB_PMD=y and that CONFIG_RTE_LIBRTE_EM_PMD=y and
that CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file


Any idea where is wrong? Thank for ur reply.

Best regards
Sothy

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
  2014-12-24 13:26 [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21 sothy shan
@ 2014-12-24 15:03 ` Masaru Oki
  2014-12-24 15:04 ` Neil Horman
  1 sibling, 0 replies; 14+ messages in thread
From: Masaru Oki @ 2014-12-24 15:03 UTC (permalink / raw)
  To: sothy shan; +Cc: dev

Hi,

> EAL: Searching for IVSHMEM devices...
> EAL: No IVSHMEM configuration found!

ivshmem is used with QEMU virtual machine.
see http://dpdk.org/doc/guides/prog_guide/ivshmem_lib.html

Try RTE_TARGET="x86_64-native-linuxapp-gcc".


2014-12-24 22:26 GMT+09:00 sothy shan <sothy.e98@gmail.com>:
> Hello!
>
> I am playing with DPDK 1.7.1 in Fedora.
>
> When I do like this:
>
> export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> make install T="$RTE_TARGET"
>
> It worked. Means Testpmd is running.
>
> When I run as mentioned below:
>
> make CONFIG_RTE_BUILD_SHARED_LIB=y  install T="$RTE_TARGET"
>
> Build is sucess. But Testpmd gives error.
>
> Error is :
>
> sudo ./x86_64-ivshmem-linuxapp-gcc/app/testpmd -c7 -n3 -- -i
> --nb-cores=2 --nb-ports=2
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 1 on socket 0
> EAL: Detected lcore 2 as core 2 on socket 0
> EAL: Detected lcore 3 as core 3 on socket 0
> EAL: Detected lcore 4 as core 0 on socket 0
> EAL: Detected lcore 5 as core 1 on socket 0
> EAL: Detected lcore 6 as core 2 on socket 0
> EAL: Detected lcore 7 as core 3 on socket 0
> EAL: Support maximum 64 logical core(s) by configuration.
> EAL: Detected 8 lcore(s)
> EAL: Searching for IVSHMEM devices...
> EAL: No IVSHMEM configuration found!
> EAL: Setting up memory...
> EAL: Ask a virtual area of 0x1c00000 bytes
> EAL: Virtual area found at 0x7f4329000000 (size = 0x1c00000)
> EAL: Ask a virtual area of 0x5c00000 bytes
> EAL: Virtual area found at 0x7f4323200000 (size = 0x5c00000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f432b600000 (size = 0x200000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f432b200000 (size = 0x200000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f432ae00000 (size = 0x200000)
> EAL: Ask a virtual area of 0x200000 bytes
> EAL: Virtual area found at 0x7f4322e00000 (size = 0x200000)
> EAL: Requesting 64 pages of size 2MB from socket 0
> EAL: TSC frequency is ~3691107 KHz
> EAL: Master core 0 is ready (tid=5053c840)
> EAL: Core 2 is ready (tid=21dfd700)
> EAL: Core 1 is ready (tid=225fe700)
> EAL: Error - exiting with code: 1
>   Cause: No probed ethernet devices - check that
> CONFIG_RTE_LIBRTE_IGB_PMD=y and that CONFIG_RTE_LIBRTE_EM_PMD=y and
> that CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file
>
>
> Any idea where is wrong? Thank for ur reply.
>
> Best regards
> Sothy

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
  2014-12-24 13:26 [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21 sothy shan
  2014-12-24 15:03 ` Masaru Oki
@ 2014-12-24 15:04 ` Neil Horman
  2014-12-25  9:11   ` sothy shan
  1 sibling, 1 reply; 14+ messages in thread
From: Neil Horman @ 2014-12-24 15:04 UTC (permalink / raw)
  To: sothy shan; +Cc: dev

On Wed, Dec 24, 2014 at 02:26:21PM +0100, sothy shan wrote:
> Hello!
> 
> I am playing with DPDK 1.7.1 in Fedora.
> 
> When I do like this:
> 
> export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> make install T="$RTE_TARGET"
> 
> It worked. Means Testpmd is running.
> 
> When I run as mentioned below:
> 
> make CONFIG_RTE_BUILD_SHARED_LIB=y  install T="$RTE_TARGET"
> 
> Build is sucess. But Testpmd gives error.
> 
> Error is :
> 
The dpdk ivshmem build assumes the presence of ivshmem devices as plumbed by
qemu virtual guests.  If you don't have a qemu guest running dpdk won't find any
shared memory devices, which is exactly what you are seeing.  That said, even if
you are running qemu guests, IIRC Fedora doesn't enable ivshmem because the code
has some security and behavioral issues still I think.  You'll need to rebuild
qemu to add support for it.

Neil

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
  2014-12-24 15:04 ` Neil Horman
@ 2014-12-25  9:11   ` sothy shan
  2014-12-25 17:08     ` Neil Horman
  0 siblings, 1 reply; 14+ messages in thread
From: sothy shan @ 2014-12-25  9:11 UTC (permalink / raw)
  To: Neil Horman; +Cc: dev

On Wed, Dec 24, 2014 at 4:04 PM, Neil Horman <nhorman@tuxdriver.com> wrote:

> On Wed, Dec 24, 2014 at 02:26:21PM +0100, sothy shan wrote:
> > Hello!
> >
> > I am playing with DPDK 1.7.1 in Fedora.
> >
> > When I do like this:
> >
> > export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> > make install T="$RTE_TARGET"
> >
> > It worked. Means Testpmd is running.
> >
> > When I run as mentioned below:
> >
> > make CONFIG_RTE_BUILD_SHARED_LIB=y  install T="$RTE_TARGET"
> >
> > Build is sucess. But Testpmd gives error.
> >
> > Error is :
> >
> The dpdk ivshmem build assumes the presence of ivshmem devices as plumbed
> by
> qemu virtual guests.  If you don't have a qemu guest running dpdk won't
> find any
> shared memory devices, which is exactly what you are seeing.  That said,
> even if
> you are running qemu guests, IIRC Fedora doesn't enable ivshmem because
> the code
> has some security and behavioral issues still I think.  You'll need to
> rebuild
> qemu to add support for it.
>

My understanding is that It is problem of enabling
CONFIG_RTE_BUILD_SHARED_LIB=y in make command, I am able to build target of
x86_64-ivshmem-linuxapp-gcc alone without shared_lib flag. I suspect an
error because of shared lib flag.

Sothy

>
> Neil
>
>

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
  2014-12-25  9:11   ` sothy shan
@ 2014-12-25 17:08     ` Neil Horman
  2014-12-26  8:01       ` sothy shan
  0 siblings, 1 reply; 14+ messages in thread
From: Neil Horman @ 2014-12-25 17:08 UTC (permalink / raw)
  To: sothy shan; +Cc: dev

On Thu, Dec 25, 2014 at 10:11:51AM +0100, sothy shan wrote:
> On Wed, Dec 24, 2014 at 4:04 PM, Neil Horman <nhorman@tuxdriver.com> wrote:
> 
> > On Wed, Dec 24, 2014 at 02:26:21PM +0100, sothy shan wrote:
> > > Hello!
> > >
> > > I am playing with DPDK 1.7.1 in Fedora.
> > >
> > > When I do like this:
> > >
> > > export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> > > make install T="$RTE_TARGET"
> > >
> > > It worked. Means Testpmd is running.
> > >
> > > When I run as mentioned below:
> > >
> > > make CONFIG_RTE_BUILD_SHARED_LIB=y  install T="$RTE_TARGET"
> > >
> > > Build is sucess. But Testpmd gives error.
> > >
> > > Error is :
> > >
> > The dpdk ivshmem build assumes the presence of ivshmem devices as plumbed
> > by
> > qemu virtual guests.  If you don't have a qemu guest running dpdk won't
> > find any
> > shared memory devices, which is exactly what you are seeing.  That said,
> > even if
> > you are running qemu guests, IIRC Fedora doesn't enable ivshmem because
> > the code
> > has some security and behavioral issues still I think.  You'll need to
> > rebuild
> > qemu to add support for it.
> >
> 
> My understanding is that It is problem of enabling
> CONFIG_RTE_BUILD_SHARED_LIB=y in make command, I am able to build target of
> x86_64-ivshmem-linuxapp-gcc alone without shared_lib flag. I suspect an
> error because of shared lib flag.
> 
What exactly do you think that problem is?  You just said in your
origional note that you are able to build the sdk and test apps without issue
(with or without building them as DSO's).  The problem comes in when you run
the app, and I expect you get the same error with both static and dynamic
builds.

The problem seems obvious to me.  DPDK cannot find any ivshmem devices on your
system when it loads (look at the code in rte_eal_ivshmem_init).  The error
message you see gets output if you don't generate an ivshmem_config, which
happens (among a few other reasons), if you don't have any ivshmem devices
created on your system

Neil

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
  2014-12-25 17:08     ` Neil Horman
@ 2014-12-26  8:01       ` sothy shan
  2014-12-26 14:37         ` Neil Horman
  0 siblings, 1 reply; 14+ messages in thread
From: sothy shan @ 2014-12-26  8:01 UTC (permalink / raw)
  To: Neil Horman; +Cc: dev

On Thu, Dec 25, 2014 at 6:08 PM, Neil Horman <nhorman@tuxdriver.com> wrote:

> On Thu, Dec 25, 2014 at 10:11:51AM +0100, sothy shan wrote:
> > On Wed, Dec 24, 2014 at 4:04 PM, Neil Horman <nhorman@tuxdriver.com>
> wrote:
> >
> > > On Wed, Dec 24, 2014 at 02:26:21PM +0100, sothy shan wrote:
> > > > Hello!
> > > >
> > > > I am playing with DPDK 1.7.1 in Fedora.
> > > >
> > > > When I do like this:
> > > >
> > > > export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> > > > make install T="$RTE_TARGET"
> > > >
> > > > It worked. Means Testpmd is running.
> > > >
> > > > When I run as mentioned below:
> > > >
> > > > make CONFIG_RTE_BUILD_SHARED_LIB=y  install T="$RTE_TARGET"
> > > >
> > > > Build is sucess. But Testpmd gives error.
> > > >
> > > > Error is :
> > > >
> > > The dpdk ivshmem build assumes the presence of ivshmem devices as
> plumbed
> > > by
> > > qemu virtual guests.  If you don't have a qemu guest running dpdk won't
> > > find any
> > > shared memory devices, which is exactly what you are seeing.  That
> said,
> > > even if
> > > you are running qemu guests, IIRC Fedora doesn't enable ivshmem because
> > > the code
> > > has some security and behavioral issues still I think.  You'll need to
> > > rebuild
> > > qemu to add support for it.
> > >
> >
> > My understanding is that It is problem of enabling
> > CONFIG_RTE_BUILD_SHARED_LIB=y in make command, I am able to build target
> of
> > x86_64-ivshmem-linuxapp-gcc alone without shared_lib flag. I suspect an
> > error because of shared lib flag.
> >
> What exactly do you think that problem is?  You just said in your
> origional note that you are able to build the sdk and test apps without
> issue
> (with or without building them as DSO's).  The problem comes in when you
> run
> the app, and I expect you get the same error with both static and dynamic
> builds.
>
> The problem seems obvious to me.  DPDK cannot find any ivshmem devices on
> your
> system when it loads (look at the code in rte_eal_ivshmem_init).  The error
> message you see gets output if you don't generate an ivshmem_config, which
> happens (among a few other reasons), if you don't have any ivshmem devices
> created on your system
>
> Neil
>


Do you have any hints for these messsages?

EAL: Error - exiting with code: 1
  Cause: No probed ethernet devices - check that
CONFIG_RTE_LIBRTE_IGB_PMD=y and that CONFIG_RTE_LIBRTE_EM_PMD=y and that
CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file


Is that with IVSHMEM device or physical devices? I guess it is physical
device problem?

Thank you

Sothy

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
  2014-12-26  8:01       ` sothy shan
@ 2014-12-26 14:37         ` Neil Horman
  2015-01-09 16:20           ` sothy shan
  0 siblings, 1 reply; 14+ messages in thread
From: Neil Horman @ 2014-12-26 14:37 UTC (permalink / raw)
  To: sothy shan; +Cc: dev

On Fri, Dec 26, 2014 at 09:01:13AM +0100, sothy shan wrote:
> On Thu, Dec 25, 2014 at 6:08 PM, Neil Horman <nhorman@tuxdriver.com> wrote:
> 
> > On Thu, Dec 25, 2014 at 10:11:51AM +0100, sothy shan wrote:
> > > On Wed, Dec 24, 2014 at 4:04 PM, Neil Horman <nhorman@tuxdriver.com>
> > wrote:
> > >
> > > > On Wed, Dec 24, 2014 at 02:26:21PM +0100, sothy shan wrote:
> > > > > Hello!
> > > > >
> > > > > I am playing with DPDK 1.7.1 in Fedora.
> > > > >
> > > > > When I do like this:
> > > > >
> > > > > export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> > > > > make install T="$RTE_TARGET"
> > > > >
> > > > > It worked. Means Testpmd is running.
> > > > >
> > > > > When I run as mentioned below:
> > > > >
> > > > > make CONFIG_RTE_BUILD_SHARED_LIB=y  install T="$RTE_TARGET"
> > > > >
> > > > > Build is sucess. But Testpmd gives error.
> > > > >
> > > > > Error is :
> > > > >
> > > > The dpdk ivshmem build assumes the presence of ivshmem devices as
> > plumbed
> > > > by
> > > > qemu virtual guests.  If you don't have a qemu guest running dpdk won't
> > > > find any
> > > > shared memory devices, which is exactly what you are seeing.  That
> > said,
> > > > even if
> > > > you are running qemu guests, IIRC Fedora doesn't enable ivshmem because
> > > > the code
> > > > has some security and behavioral issues still I think.  You'll need to
> > > > rebuild
> > > > qemu to add support for it.
> > > >
> > >
> > > My understanding is that It is problem of enabling
> > > CONFIG_RTE_BUILD_SHARED_LIB=y in make command, I am able to build target
> > of
> > > x86_64-ivshmem-linuxapp-gcc alone without shared_lib flag. I suspect an
> > > error because of shared lib flag.
> > >
> > What exactly do you think that problem is?  You just said in your
> > origional note that you are able to build the sdk and test apps without
> > issue
> > (with or without building them as DSO's).  The problem comes in when you
> > run
> > the app, and I expect you get the same error with both static and dynamic
> > builds.
> >
> > The problem seems obvious to me.  DPDK cannot find any ivshmem devices on
> > your
> > system when it loads (look at the code in rte_eal_ivshmem_init).  The error
> > message you see gets output if you don't generate an ivshmem_config, which
> > happens (among a few other reasons), if you don't have any ivshmem devices
> > created on your system
> >
> > Neil
> >
> 
> 
> Do you have any hints for these messsages?
> 
Yes, I gave you direction in my last note, its the fact that no ivshmem devices
were found.

> EAL: Error - exiting with code: 1
>   Cause: No probed ethernet devices - check that
> CONFIG_RTE_LIBRTE_IGB_PMD=y and that CONFIG_RTE_LIBRTE_EM_PMD=y and that
> CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file
> 
This is a false indicator.  If you look at a later version of the code you'll
see that the message has been pruned to just indicate that no probed ethernet
devices were found.  The remainder of the message was there because it used to
be a presumption that a physical devices was in use, which need not be the case.
Like I said before you need an ivshmem driver, which qemu provides, but not in
the current fedora build.

> 
> Is that with IVSHMEM device or physical devices? I guess it is physical
> device problem?
> 
No, its not, you're making this harder than it needs to be.  google qemu and
ivshmem and you'll see.  Heres an article to get you started:
http://lwn.net/Articles/380869/
Neil

> Thank you
> 
> Sothy

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
  2014-12-26 14:37         ` Neil Horman
@ 2015-01-09 16:20           ` sothy shan
  2015-01-10 12:44             ` Neil Horman
  0 siblings, 1 reply; 14+ messages in thread
From: sothy shan @ 2015-01-09 16:20 UTC (permalink / raw)
  To: Neil Horman; +Cc: dev

According to your argument,

I compiled qemu in DPDK OVS as provided with command.

After that, I compiled as stated here.

cd DPDK                     # DPDK sub-directoryexport
RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y
install T="$RTE_TARGET"

Then I try to run the command for testpmd. I got same error. Any idea
where is the mistake? Thanks

DPDK 1.7.1 in Fedora 21. PLease see the error here





[cubiq@localhost dpdk-1.7.1]$ sudo
./x86_64-ivshmem-linuxapp-gcc/app/testpmd -c7 -n3 -- -i --nb-cores=2
--nb-ports=2
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 0 on socket 0
EAL: Detected lcore 5 as core 1 on socket 0
EAL: Detected lcore 6 as core 2 on socket 0
EAL: Detected lcore 7 as core 3 on socket 0
EAL: Support maximum 64 logical core(s) by configuration.
EAL: Detected 8 lcore(s)
EAL: Searching for IVSHMEM devices...
EAL: No IVSHMEM configuration found!
EAL: Setting up memory...
EAL: Ask a virtual area of 0x1800000 bytes
EAL: Virtual area found at 0x7fbe51000000 (size = 0x1800000)
EAL: Ask a virtual area of 0x1400000 bytes
EAL: Virtual area found at 0x7fbe4fa00000 (size = 0x1400000)
EAL: Ask a virtual area of 0x800000 bytes
EAL: Virtual area found at 0x7fbe52a00000 (size = 0x800000)
EAL: Ask a virtual area of 0x2000000 bytes
EAL: Virtual area found at 0x7fbe4d800000 (size = 0x2000000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7fbe4d200000 (size = 0x400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7fbe4cc00000 (size = 0x400000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7fbe4c600000 (size = 0x400000)
EAL: Ask a virtual area of 0x1c00000 bytes
EAL: Virtual area found at 0x7fbe4a800000 (size = 0x1c00000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7fbe4a200000 (size = 0x400000)
EAL: Requesting 64 pages of size 2MB from socket 0
EAL: TSC frequency is ~3691108 KHz
EAL: Master core 0 is ready (tid=98377940)
EAL: Core 2 is ready (tid=491fd700)
EAL: Core 1 is ready (tid=499fe700)
EAL: PCI device 0000:06:00.0 on NUMA socket 0
EAL:   probe driver: 8086:154d rte_ixgbe_pmd
EAL:   0000:06:00.0 not managed by VFIO driver, skipping
EAL:   0000:06:00.0 not managed by UIO driver, skipping
EAL: PCI device 0000:06:00.1 on NUMA socket 0
EAL:   probe driver: 8086:154d rte_ixgbe_pmd
EAL:   0000:06:00.1 not managed by VFIO driver, skipping
EAL:   0000:06:00.1 not managed by UIO driver, skipping
EAL: Error - exiting with code: 1
  Cause: No probed ethernet devices - check that
CONFIG_RTE_LIBRTE_IGB_PMD=y and that CONFIG_RTE_LIBRTE_EM_PMD=y and that
CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file



On Fri, Dec 26, 2014 at 3:37 PM, Neil Horman <nhorman@tuxdriver.com> wrote:

> On Fri, Dec 26, 2014 at 09:01:13AM +0100, sothy shan wrote:
> > On Thu, Dec 25, 2014 at 6:08 PM, Neil Horman <nhorman@tuxdriver.com>
> wrote:
> >
> > > On Thu, Dec 25, 2014 at 10:11:51AM +0100, sothy shan wrote:
> > > > On Wed, Dec 24, 2014 at 4:04 PM, Neil Horman <nhorman@tuxdriver.com>
> > > wrote:
> > > >
> > > > > On Wed, Dec 24, 2014 at 02:26:21PM +0100, sothy shan wrote:
> > > > > > Hello!
> > > > > >
> > > > > > I am playing with DPDK 1.7.1 in Fedora.
> > > > > >
> > > > > > When I do like this:
> > > > > >
> > > > > > export RTE_SDK=$(pwd)export
> RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> > > > > > make install T="$RTE_TARGET"
> > > > > >
> > > > > > It worked. Means Testpmd is running.
> > > > > >
> > > > > > When I run as mentioned below:
> > > > > >
> > > > > > make CONFIG_RTE_BUILD_SHARED_LIB=y  install T="$RTE_TARGET"
> > > > > >
> > > > > > Build is sucess. But Testpmd gives error.
> > > > > >
> > > > > > Error is :
> > > > > >
> > > > > The dpdk ivshmem build assumes the presence of ivshmem devices as
> > > plumbed
> > > > > by
> > > > > qemu virtual guests.  If you don't have a qemu guest running dpdk
> won't
> > > > > find any
> > > > > shared memory devices, which is exactly what you are seeing.  That
> > > said,
> > > > > even if
> > > > > you are running qemu guests, IIRC Fedora doesn't enable ivshmem
> because
> > > > > the code
> > > > > has some security and behavioral issues still I think.  You'll
> need to
> > > > > rebuild
> > > > > qemu to add support for it.
> > > > >
> > > >
> > > > My understanding is that It is problem of enabling
> > > > CONFIG_RTE_BUILD_SHARED_LIB=y in make command, I am able to build
> target
> > > of
> > > > x86_64-ivshmem-linuxapp-gcc alone without shared_lib flag. I suspect
> an
> > > > error because of shared lib flag.
> > > >
> > > What exactly do you think that problem is?  You just said in your
> > > origional note that you are able to build the sdk and test apps without
> > > issue
> > > (with or without building them as DSO's).  The problem comes in when
> you
> > > run
> > > the app, and I expect you get the same error with both static and
> dynamic
> > > builds.
> > >
> > > The problem seems obvious to me.  DPDK cannot find any ivshmem devices
> on
> > > your
> > > system when it loads (look at the code in rte_eal_ivshmem_init).  The
> error
> > > message you see gets output if you don't generate an ivshmem_config,
> which
> > > happens (among a few other reasons), if you don't have any ivshmem
> devices
> > > created on your system
> > >
> > > Neil
> > >
> >
> >
> > Do you have any hints for these messsages?
> >
> Yes, I gave you direction in my last note, its the fact that no ivshmem
> devices
> were found.
>
> > EAL: Error - exiting with code: 1
> >   Cause: No probed ethernet devices - check that
> > CONFIG_RTE_LIBRTE_IGB_PMD=y and that CONFIG_RTE_LIBRTE_EM_PMD=y and that
> > CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file
> >
> This is a false indicator.  If you look at a later version of the code
> you'll
> see that the message has been pruned to just indicate that no probed
> ethernet
> devices were found.  The remainder of the message was there because it
> used to
> be a presumption that a physical devices was in use, which need not be the
> case.
> Like I said before you need an ivshmem driver, which qemu provides, but
> not in
> the current fedora build.
>
> >
> > Is that with IVSHMEM device or physical devices? I guess it is physical
> > device problem?
> >
> No, its not, you're making this harder than it needs to be.  google qemu
> and
> ivshmem and you'll see.  Heres an article to get you started:
> http://lwn.net/Articles/380869/
> Neil
>
> > Thank you
> >
> > Sothy
>

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
  2015-01-09 16:20           ` sothy shan
@ 2015-01-10 12:44             ` Neil Horman
  2015-01-16 14:10               ` sothy shan
  0 siblings, 1 reply; 14+ messages in thread
From: Neil Horman @ 2015-01-10 12:44 UTC (permalink / raw)
  To: sothy shan; +Cc: dev

On Fri, Jan 09, 2015 at 05:20:31PM +0100, sothy shan wrote:
> According to your argument,
> 
> I compiled qemu in DPDK OVS as provided with command.
> 
> After that, I compiled as stated here.
> 
> cd DPDK                     # DPDK sub-directoryexport
> RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y
> install T="$RTE_TARGET"
> 
> Then I try to run the command for testpmd. I got same error. Any idea
> where is the mistake? Thanks
> 
> DPDK 1.7.1 in Fedora 21. PLease see the error here
> 
> 
Did you run qemu and create an ivshmem device?  Thats why you needed qemu
support so that you could run it and have qemu create a network device that had
a ivshmem interface
Neil

> 
> 
> 
> [cubiq@localhost dpdk-1.7.1]$ sudo
> ./x86_64-ivshmem-linuxapp-gcc/app/testpmd -c7 -n3 -- -i --nb-cores=2
> --nb-ports=2
> EAL: Detected lcore 0 as core 0 on socket 0
> EAL: Detected lcore 1 as core 1 on socket 0
> EAL: Detected lcore 2 as core 2 on socket 0
> EAL: Detected lcore 3 as core 3 on socket 0
> EAL: Detected lcore 4 as core 0 on socket 0
> EAL: Detected lcore 5 as core 1 on socket 0
> EAL: Detected lcore 6 as core 2 on socket 0
> EAL: Detected lcore 7 as core 3 on socket 0
> EAL: Support maximum 64 logical core(s) by configuration.
> EAL: Detected 8 lcore(s)
> EAL: Searching for IVSHMEM devices...
> EAL: No IVSHMEM configuration found!
> EAL: Setting up memory...
> EAL: Ask a virtual area of 0x1800000 bytes
> EAL: Virtual area found at 0x7fbe51000000 (size = 0x1800000)
> EAL: Ask a virtual area of 0x1400000 bytes
> EAL: Virtual area found at 0x7fbe4fa00000 (size = 0x1400000)
> EAL: Ask a virtual area of 0x800000 bytes
> EAL: Virtual area found at 0x7fbe52a00000 (size = 0x800000)
> EAL: Ask a virtual area of 0x2000000 bytes
> EAL: Virtual area found at 0x7fbe4d800000 (size = 0x2000000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7fbe4d200000 (size = 0x400000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7fbe4cc00000 (size = 0x400000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7fbe4c600000 (size = 0x400000)
> EAL: Ask a virtual area of 0x1c00000 bytes
> EAL: Virtual area found at 0x7fbe4a800000 (size = 0x1c00000)
> EAL: Ask a virtual area of 0x400000 bytes
> EAL: Virtual area found at 0x7fbe4a200000 (size = 0x400000)
> EAL: Requesting 64 pages of size 2MB from socket 0
> EAL: TSC frequency is ~3691108 KHz
> EAL: Master core 0 is ready (tid=98377940)
> EAL: Core 2 is ready (tid=491fd700)
> EAL: Core 1 is ready (tid=499fe700)
> EAL: PCI device 0000:06:00.0 on NUMA socket 0
> EAL:   probe driver: 8086:154d rte_ixgbe_pmd
> EAL:   0000:06:00.0 not managed by VFIO driver, skipping
> EAL:   0000:06:00.0 not managed by UIO driver, skipping
> EAL: PCI device 0000:06:00.1 on NUMA socket 0
> EAL:   probe driver: 8086:154d rte_ixgbe_pmd
> EAL:   0000:06:00.1 not managed by VFIO driver, skipping
> EAL:   0000:06:00.1 not managed by UIO driver, skipping
> EAL: Error - exiting with code: 1
>   Cause: No probed ethernet devices - check that
> CONFIG_RTE_LIBRTE_IGB_PMD=y and that CONFIG_RTE_LIBRTE_EM_PMD=y and that
> CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file
> 
> 
> 
> On Fri, Dec 26, 2014 at 3:37 PM, Neil Horman <nhorman@tuxdriver.com> wrote:
> 
> > On Fri, Dec 26, 2014 at 09:01:13AM +0100, sothy shan wrote:
> > > On Thu, Dec 25, 2014 at 6:08 PM, Neil Horman <nhorman@tuxdriver.com>
> > wrote:
> > >
> > > > On Thu, Dec 25, 2014 at 10:11:51AM +0100, sothy shan wrote:
> > > > > On Wed, Dec 24, 2014 at 4:04 PM, Neil Horman <nhorman@tuxdriver.com>
> > > > wrote:
> > > > >
> > > > > > On Wed, Dec 24, 2014 at 02:26:21PM +0100, sothy shan wrote:
> > > > > > > Hello!
> > > > > > >
> > > > > > > I am playing with DPDK 1.7.1 in Fedora.
> > > > > > >
> > > > > > > When I do like this:
> > > > > > >
> > > > > > > export RTE_SDK=$(pwd)export
> > RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> > > > > > > make install T="$RTE_TARGET"
> > > > > > >
> > > > > > > It worked. Means Testpmd is running.
> > > > > > >
> > > > > > > When I run as mentioned below:
> > > > > > >
> > > > > > > make CONFIG_RTE_BUILD_SHARED_LIB=y  install T="$RTE_TARGET"
> > > > > > >
> > > > > > > Build is sucess. But Testpmd gives error.
> > > > > > >
> > > > > > > Error is :
> > > > > > >
> > > > > > The dpdk ivshmem build assumes the presence of ivshmem devices as
> > > > plumbed
> > > > > > by
> > > > > > qemu virtual guests.  If you don't have a qemu guest running dpdk
> > won't
> > > > > > find any
> > > > > > shared memory devices, which is exactly what you are seeing.  That
> > > > said,
> > > > > > even if
> > > > > > you are running qemu guests, IIRC Fedora doesn't enable ivshmem
> > because
> > > > > > the code
> > > > > > has some security and behavioral issues still I think.  You'll
> > need to
> > > > > > rebuild
> > > > > > qemu to add support for it.
> > > > > >
> > > > >
> > > > > My understanding is that It is problem of enabling
> > > > > CONFIG_RTE_BUILD_SHARED_LIB=y in make command, I am able to build
> > target
> > > > of
> > > > > x86_64-ivshmem-linuxapp-gcc alone without shared_lib flag. I suspect
> > an
> > > > > error because of shared lib flag.
> > > > >
> > > > What exactly do you think that problem is?  You just said in your
> > > > origional note that you are able to build the sdk and test apps without
> > > > issue
> > > > (with or without building them as DSO's).  The problem comes in when
> > you
> > > > run
> > > > the app, and I expect you get the same error with both static and
> > dynamic
> > > > builds.
> > > >
> > > > The problem seems obvious to me.  DPDK cannot find any ivshmem devices
> > on
> > > > your
> > > > system when it loads (look at the code in rte_eal_ivshmem_init).  The
> > error
> > > > message you see gets output if you don't generate an ivshmem_config,
> > which
> > > > happens (among a few other reasons), if you don't have any ivshmem
> > devices
> > > > created on your system
> > > >
> > > > Neil
> > > >
> > >
> > >
> > > Do you have any hints for these messsages?
> > >
> > Yes, I gave you direction in my last note, its the fact that no ivshmem
> > devices
> > were found.
> >
> > > EAL: Error - exiting with code: 1
> > >   Cause: No probed ethernet devices - check that
> > > CONFIG_RTE_LIBRTE_IGB_PMD=y and that CONFIG_RTE_LIBRTE_EM_PMD=y and that
> > > CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file
> > >
> > This is a false indicator.  If you look at a later version of the code
> > you'll
> > see that the message has been pruned to just indicate that no probed
> > ethernet
> > devices were found.  The remainder of the message was there because it
> > used to
> > be a presumption that a physical devices was in use, which need not be the
> > case.
> > Like I said before you need an ivshmem driver, which qemu provides, but
> > not in
> > the current fedora build.
> >
> > >
> > > Is that with IVSHMEM device or physical devices? I guess it is physical
> > > device problem?
> > >
> > No, its not, you're making this harder than it needs to be.  google qemu
> > and
> > ivshmem and you'll see.  Heres an article to get you started:
> > http://lwn.net/Articles/380869/
> > Neil
> >
> > > Thank you
> > >
> > > Sothy
> >

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
  2015-01-10 12:44             ` Neil Horman
@ 2015-01-16 14:10               ` sothy shan
  2015-01-16 14:27                 ` Olivier MATZ
  0 siblings, 1 reply; 14+ messages in thread
From: sothy shan @ 2015-01-16 14:10 UTC (permalink / raw)
  To: Neil Horman; +Cc: dev

I guess you are completely wrong.

Becasue when I do

make config T=x86_64-ivshmem-linuxapp-gcc
make

Testpmd works.

When I do  with

export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y
install T="$RTE_TARGET"


I get same error. I guess there are some problems in above two config
variables. I see some email post over some changes.But I didnt get the
point, but working on it.

It is just information for you.


Best regards

Sothy



On Sat, Jan 10, 2015 at 1:44 PM, Neil Horman <nhorman@tuxdriver.com> wrote:

> On Fri, Jan 09, 2015 at 05:20:31PM +0100, sothy shan wrote:
> > According to your argument,
> >
> > I compiled qemu in DPDK OVS as provided with command.
> >
> > After that, I compiled as stated here.
> >
> > cd DPDK                     # DPDK sub-directoryexport
> > RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> > make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y
> > install T="$RTE_TARGET"
> >
> > Then I try to run the command for testpmd. I got same error. Any idea
> > where is the mistake? Thanks
> >
> > DPDK 1.7.1 in Fedora 21. PLease see the error here
> >
> >
> Did you run qemu and create an ivshmem device?  Thats why you needed qemu
> support so that you could run it and have qemu create a network device
> that had
> a ivshmem interface
> Neil
>
> >
> >
> >
> > [cubiq@localhost dpdk-1.7.1]$ sudo
> > ./x86_64-ivshmem-linuxapp-gcc/app/testpmd -c7 -n3 -- -i --nb-cores=2
> > --nb-ports=2
> > EAL: Detected lcore 0 as core 0 on socket 0
> > EAL: Detected lcore 1 as core 1 on socket 0
> > EAL: Detected lcore 2 as core 2 on socket 0
> > EAL: Detected lcore 3 as core 3 on socket 0
> > EAL: Detected lcore 4 as core 0 on socket 0
> > EAL: Detected lcore 5 as core 1 on socket 0
> > EAL: Detected lcore 6 as core 2 on socket 0
> > EAL: Detected lcore 7 as core 3 on socket 0
> > EAL: Support maximum 64 logical core(s) by configuration.
> > EAL: Detected 8 lcore(s)
> > EAL: Searching for IVSHMEM devices...
> > EAL: No IVSHMEM configuration found!
> > EAL: Setting up memory...
> > EAL: Ask a virtual area of 0x1800000 bytes
> > EAL: Virtual area found at 0x7fbe51000000 (size = 0x1800000)
> > EAL: Ask a virtual area of 0x1400000 bytes
> > EAL: Virtual area found at 0x7fbe4fa00000 (size = 0x1400000)
> > EAL: Ask a virtual area of 0x800000 bytes
> > EAL: Virtual area found at 0x7fbe52a00000 (size = 0x800000)
> > EAL: Ask a virtual area of 0x2000000 bytes
> > EAL: Virtual area found at 0x7fbe4d800000 (size = 0x2000000)
> > EAL: Ask a virtual area of 0x400000 bytes
> > EAL: Virtual area found at 0x7fbe4d200000 (size = 0x400000)
> > EAL: Ask a virtual area of 0x400000 bytes
> > EAL: Virtual area found at 0x7fbe4cc00000 (size = 0x400000)
> > EAL: Ask a virtual area of 0x400000 bytes
> > EAL: Virtual area found at 0x7fbe4c600000 (size = 0x400000)
> > EAL: Ask a virtual area of 0x1c00000 bytes
> > EAL: Virtual area found at 0x7fbe4a800000 (size = 0x1c00000)
> > EAL: Ask a virtual area of 0x400000 bytes
> > EAL: Virtual area found at 0x7fbe4a200000 (size = 0x400000)
> > EAL: Requesting 64 pages of size 2MB from socket 0
> > EAL: TSC frequency is ~3691108 KHz
> > EAL: Master core 0 is ready (tid=98377940)
> > EAL: Core 2 is ready (tid=491fd700)
> > EAL: Core 1 is ready (tid=499fe700)
> > EAL: PCI device 0000:06:00.0 on NUMA socket 0
> > EAL:   probe driver: 8086:154d rte_ixgbe_pmd
> > EAL:   0000:06:00.0 not managed by VFIO driver, skipping
> > EAL:   0000:06:00.0 not managed by UIO driver, skipping
> > EAL: PCI device 0000:06:00.1 on NUMA socket 0
> > EAL:   probe driver: 8086:154d rte_ixgbe_pmd
> > EAL:   0000:06:00.1 not managed by VFIO driver, skipping
> > EAL:   0000:06:00.1 not managed by UIO driver, skipping
> > EAL: Error - exiting with code: 1
> >   Cause: No probed ethernet devices - check that
> > CONFIG_RTE_LIBRTE_IGB_PMD=y and that CONFIG_RTE_LIBRTE_EM_PMD=y and that
> > CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file
> >
> >
> >
> > On Fri, Dec 26, 2014 at 3:37 PM, Neil Horman <nhorman@tuxdriver.com>
> wrote:
> >
> > > On Fri, Dec 26, 2014 at 09:01:13AM +0100, sothy shan wrote:
> > > > On Thu, Dec 25, 2014 at 6:08 PM, Neil Horman <nhorman@tuxdriver.com>
> > > wrote:
> > > >
> > > > > On Thu, Dec 25, 2014 at 10:11:51AM +0100, sothy shan wrote:
> > > > > > On Wed, Dec 24, 2014 at 4:04 PM, Neil Horman <
> nhorman@tuxdriver.com>
> > > > > wrote:
> > > > > >
> > > > > > > On Wed, Dec 24, 2014 at 02:26:21PM +0100, sothy shan wrote:
> > > > > > > > Hello!
> > > > > > > >
> > > > > > > > I am playing with DPDK 1.7.1 in Fedora.
> > > > > > > >
> > > > > > > > When I do like this:
> > > > > > > >
> > > > > > > > export RTE_SDK=$(pwd)export
> > > RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> > > > > > > > make install T="$RTE_TARGET"
> > > > > > > >
> > > > > > > > It worked. Means Testpmd is running.
> > > > > > > >
> > > > > > > > When I run as mentioned below:
> > > > > > > >
> > > > > > > > make CONFIG_RTE_BUILD_SHARED_LIB=y  install T="$RTE_TARGET"
> > > > > > > >
> > > > > > > > Build is sucess. But Testpmd gives error.
> > > > > > > >
> > > > > > > > Error is :
> > > > > > > >
> > > > > > > The dpdk ivshmem build assumes the presence of ivshmem devices
> as
> > > > > plumbed
> > > > > > > by
> > > > > > > qemu virtual guests.  If you don't have a qemu guest running
> dpdk
> > > won't
> > > > > > > find any
> > > > > > > shared memory devices, which is exactly what you are seeing.
> That
> > > > > said,
> > > > > > > even if
> > > > > > > you are running qemu guests, IIRC Fedora doesn't enable ivshmem
> > > because
> > > > > > > the code
> > > > > > > has some security and behavioral issues still I think.  You'll
> > > need to
> > > > > > > rebuild
> > > > > > > qemu to add support for it.
> > > > > > >
> > > > > >
> > > > > > My understanding is that It is problem of enabling
> > > > > > CONFIG_RTE_BUILD_SHARED_LIB=y in make command, I am able to build
> > > target
> > > > > of
> > > > > > x86_64-ivshmem-linuxapp-gcc alone without shared_lib flag. I
> suspect
> > > an
> > > > > > error because of shared lib flag.
> > > > > >
> > > > > What exactly do you think that problem is?  You just said in your
> > > > > origional note that you are able to build the sdk and test apps
> without
> > > > > issue
> > > > > (with or without building them as DSO's).  The problem comes in
> when
> > > you
> > > > > run
> > > > > the app, and I expect you get the same error with both static and
> > > dynamic
> > > > > builds.
> > > > >
> > > > > The problem seems obvious to me.  DPDK cannot find any ivshmem
> devices
> > > on
> > > > > your
> > > > > system when it loads (look at the code in rte_eal_ivshmem_init).
> The
> > > error
> > > > > message you see gets output if you don't generate an
> ivshmem_config,
> > > which
> > > > > happens (among a few other reasons), if you don't have any ivshmem
> > > devices
> > > > > created on your system
> > > > >
> > > > > Neil
> > > > >
> > > >
> > > >
> > > > Do you have any hints for these messsages?
> > > >
> > > Yes, I gave you direction in my last note, its the fact that no ivshmem
> > > devices
> > > were found.
> > >
> > > > EAL: Error - exiting with code: 1
> > > >   Cause: No probed ethernet devices - check that
> > > > CONFIG_RTE_LIBRTE_IGB_PMD=y and that CONFIG_RTE_LIBRTE_EM_PMD=y and
> that
> > > > CONFIG_RTE_LIBRTE_IXGBE_PMD=y in your configuration file
> > > >
> > > This is a false indicator.  If you look at a later version of the code
> > > you'll
> > > see that the message has been pruned to just indicate that no probed
> > > ethernet
> > > devices were found.  The remainder of the message was there because it
> > > used to
> > > be a presumption that a physical devices was in use, which need not be
> the
> > > case.
> > > Like I said before you need an ivshmem driver, which qemu provides, but
> > > not in
> > > the current fedora build.
> > >
> > > >
> > > > Is that with IVSHMEM device or physical devices? I guess it is
> physical
> > > > device problem?
> > > >
> > > No, its not, you're making this harder than it needs to be.  google
> qemu
> > > and
> > > ivshmem and you'll see.  Heres an article to get you started:
> > > http://lwn.net/Articles/380869/
> > > Neil
> > >
> > > > Thank you
> > > >
> > > > Sothy
> > >
>

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
  2015-01-16 14:10               ` sothy shan
@ 2015-01-16 14:27                 ` Olivier MATZ
  2015-01-16 16:07                   ` sothy shan
  0 siblings, 1 reply; 14+ messages in thread
From: Olivier MATZ @ 2015-01-16 14:27 UTC (permalink / raw)
  To: sothy shan, Neil Horman; +Cc: dev

Hi Sothy,

On 01/16/2015 03:10 PM, sothy shan wrote:
> I guess you are completely wrong.
> 
> Becasue when I do
> 
> make config T=x86_64-ivshmem-linuxapp-gcc
> make
> 
> Testpmd works.
> 
> When I do  with
> 
> export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
> make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y
> install T="$RTE_TARGET"

Are you sure that this syntax is supported by the build system?

As far as I know, RTE_SDK and RTE_TARGET must be defined when building
an external application (like in examples), not when building test-pmd
app which is a sdk built-in.

Also, I'm not sure passing a CONFIG_XYZ=y variable will be properly
taken in account by the build system. Where did you found this syntax?
The proper way is:

  make config T=x86_64-ivshmem-linuxapp-gcc O=my_dir
  ${EDITOR} my_dir/.config
  make O=my_dir

One last comment, please be careful when copy/pasting commands in
mails as there are typos in some of your commands. A reader could
expect that your problem comes from this:

  $ export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
  $ echo $RTE_SDK
  /home/userexport

Regards,
Olivier

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
  2015-01-16 14:27                 ` Olivier MATZ
@ 2015-01-16 16:07                   ` sothy shan
  2015-01-16 16:35                     ` Olivier MATZ
  0 siblings, 1 reply; 14+ messages in thread
From: sothy shan @ 2015-01-16 16:07 UTC (permalink / raw)
  To: Olivier MATZ; +Cc: dev

On Fri, Jan 16, 2015 at 3:27 PM, Olivier MATZ <olivier.matz@6wind.com> wrote:
> Hi Sothy,
>
> On 01/16/2015 03:10 PM, sothy shan wrote:
>> I guess you are completely wrong.
>>
>> Becasue when I do
>>
>> make config T=x86_64-ivshmem-linuxapp-gcc
>> make
>>
>> Testpmd works.
>>
>> When I do  with
>>
>> export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
>> make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y
>> install T="$RTE_TARGET"
>
> Are you sure that this syntax is supported by the build system?

I am tryiting to build DPDK OVS and found  the instruction in
https://github.com/01org/dpdk-ovs/blob/development/docs/01_Installation.md


>
> As far as I know, RTE_SDK and RTE_TARGET must be defined when building
> an external application (like in examples), not when building test-pmd
> app which is a sdk built-in.

If I understand the your idea, I should compile and run DPDK OVS
directly rather than DPDK testpmd. Isnt it? I will try now this.

Before, I tries testpmd and then go for DPDK OVS.

>
> Also, I'm not sure passing a CONFIG_XYZ=y variable will be properly
> taken in account by the build system. Where did you found this syntax?

https://github.com/01org/dpdk-ovs/blob/development/docs/01_Installation.md

> The proper way is:
>
>   make config T=x86_64-ivshmem-linuxapp-gcc O=my_dir
>   ${EDITOR} my_dir/.config
>   make O=my_dir
>
> One last comment, please be careful when copy/pasting commands in
> mails as there are typos in some of your commands. A reader could
> expect that your problem comes from this:
>
>   $ export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
>   $ echo $RTE_SDK
>   /home/userexport
>

Sorry for mistake and I will do with care nw.

> Regards,
> Olivier

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
  2015-01-16 16:07                   ` sothy shan
@ 2015-01-16 16:35                     ` Olivier MATZ
  2015-01-16 16:47                       ` sothy shan
  0 siblings, 1 reply; 14+ messages in thread
From: Olivier MATZ @ 2015-01-16 16:35 UTC (permalink / raw)
  To: sothy shan; +Cc: dev

Hi Sothy,

On 01/16/2015 05:07 PM, sothy shan wrote:
> On Fri, Jan 16, 2015 at 3:27 PM, Olivier MATZ <olivier.matz@6wind.com> wrote:
>>> When I do  with
>>>
>>> export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
>>> make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y
>>> install T="$RTE_TARGET"
>>
>> Are you sure that this syntax is supported by the build system?
> 
> I am tryiting to build DPDK OVS and found  the instruction in
> https://github.com/01org/dpdk-ovs/blob/development/docs/01_Installation.md

I just noticed the syntax is strange, you can check the supported
options here:

http://dpdk.org/doc/guides/prog_guide/dev_kit_build_system.html#makefile-description

I'm not sure the CONFIG_ will be taken in account when generating
rte_config.h (see rte.sdkconfig.mk and scripts/gen-config-h.sh). But
maybe it's not related to your issue.

Regards,
Olivier

^ permalink raw reply	[flat|nested] 14+ messages in thread

* Re: [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21
  2015-01-16 16:35                     ` Olivier MATZ
@ 2015-01-16 16:47                       ` sothy shan
  0 siblings, 0 replies; 14+ messages in thread
From: sothy shan @ 2015-01-16 16:47 UTC (permalink / raw)
  To: Olivier MATZ; +Cc: dev

On Fri, Jan 16, 2015 at 5:35 PM, Olivier MATZ <olivier.matz@6wind.com> wrote:
> Hi Sothy,
>
> On 01/16/2015 05:07 PM, sothy shan wrote:
>> On Fri, Jan 16, 2015 at 3:27 PM, Olivier MATZ <olivier.matz@6wind.com> wrote:
>>>> When I do  with
>>>>
>>>> export RTE_SDK=$(pwd)export RTE_TARGET="x86_64-ivshmem-linuxapp-gcc"
>>>> make CONFIG_RTE_BUILD_COMBINE_LIBS=y CONFIG_RTE_BUILD_SHARED_LIB=y
>>>> install T="$RTE_TARGET"
>>>
>>> Are you sure that this syntax is supported by the build system?
>>
>> I am tryiting to build DPDK OVS and found  the instruction in
>> https://github.com/01org/dpdk-ovs/blob/development/docs/01_Installation.md
>
> I just noticed the syntax is strange, you can check the supported
> options here:
>
> http://dpdk.org/doc/guides/prog_guide/dev_kit_build_system.html#makefile-description

For me, I followed the top leve compilation and compilation went well.
https://github.com/01org/dpdk-ovs/blob/development/docs/01_Installation.md
It means those paremeters are taken into account somewhere.

Now I didnt check testpmd command and directly went to run ovs-dpdk in
Fedora 20 with DPDK OVS 1.2

I am in another problem. I guess it is out of your focus, I just give
you the idea.

££££££££££££££££££££££££££££££££££££££££

sudo ./datapath/dpdk/ovs-dpdk -c 0x1E -n 4 --proc

                                                                -type
primary --huge-dir=/mnt/huge -- --stats_core=4 --stats=5 -p 0x07
EAL: Detected lcore 0 as core 0 on socket 0
EAL: Detected lcore 1 as core 1 on socket 0
EAL: Detected lcore 2 as core 2 on socket 0
EAL: Detected lcore 3 as core 3 on socket 0
EAL: Detected lcore 4 as core 0 on socket 0
EAL: Detected lcore 5 as core 1 on socket 0
EAL: Detected lcore 6 as core 2 on socket 0
EAL: Detected lcore 7 as core 3 on socket 0
EAL: Support maximum 64 logical core(s) by configuration.
EAL: Detected 8 lcore(s)
EAL:   cannot open VFIO container, error 2 (No such file or directory)
EAL: VFIO support could not be initialized
EAL: Searching for IVSHMEM devices...
EAL: No IVSHMEM configuration found!
EAL: Setting up memory...
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7fcb5b400000 (size = 0x200000)
EAL: Ask a virtual area of 0x3000000 bytes
EAL: Virtual area found at 0x7fcb58200000 (size = 0x3000000)
EAL: Ask a virtual area of 0x3800000 bytes
EAL: Virtual area found at 0x7fcb54800000 (size = 0x3800000)
EAL: Ask a virtual area of 0x1000000 bytes
EAL: Virtual area found at 0x7fcb53600000 (size = 0x1000000)
EAL: Ask a virtual area of 0x400000 bytes
EAL: Virtual area found at 0x7fcb53000000 (size = 0x400000)
EAL: Ask a virtual area of 0x200000 bytes
EAL: Virtual area found at 0x7fcb52c00000 (size = 0x200000)
EAL: Requesting 64 pages of size 2MB from socket 0
EAL: TSC frequency is ~3691107 KHz
EAL: Master core 1 is ready (tid=5b701940)
EAL: Core 4 is ready (tid=513fc700)
EAL: Core 3 is ready (tid=51bfd700)
EAL: Core 2 is ready (tid=523fe700)
EAL: PCI device 0000:03:00.0 on NUMA socket -1
EAL:   probe driver: 8086:150e rte_igb_pmd
EAL:   PCI memory mapped at 0x7fcb5b645000
EAL:   PCI memory mapped at 0x7fcb5b70a000
EAL: PCI device 0000:03:00.1 on NUMA socket -1
EAL:   probe driver: 8086:150e rte_igb_pmd
EAL:   PCI memory mapped at 0x7fcb5b380000
EAL:   PCI memory mapped at 0x7fcb5b706000
EAL: PCI device 0000:03:00.2 on NUMA socket -1
EAL:   probe driver: 8086:150e rte_igb_pmd
EAL:   PCI memory mapped at 0x7fcb5b300000
EAL:   PCI memory mapped at 0x7fcb5b641000
EAL: PCI device 0000:03:00.3 on NUMA socket -1
EAL:   probe driver: 8086:150e rte_igb_pmd
EAL:   PCI memory mapped at 0x7fcb5b280000
EAL:   PCI memory mapped at 0x7fcb5b63d000
EAL: PCI device 0000:06:00.0 on NUMA socket -1
EAL:   probe driver: 8086:154d rte_ixgbe_pmd
EAL:   0000:06:00.0 not managed by UIO driver, skipping
EAL: PCI device 0000:06:00.1 on NUMA socket -1
EAL:   probe driver: 8086:154d rte_ixgbe_pmd
EAL:   0000:06:00.1 not managed by UIO driver, skipping
PANIC in ovdk_mempools_init():
Cannot create ctrlmbuf mempool 'OVDK_Ctrlmbuf_Mempool' (Cannot allocate memory)
1: [/home/cubiq/sothy/dpdk-1.7.1/x86_64-ivshmem-linuxapp-gcc/lib/libintel_dpdk.s


              o(rte_dump_stack+0x18) [0x7fcb5b7922d8]]


 £££££££££££££££££££££££££££££££££££££££££££££££££££££££££££££
>
> I'm not sure the CONFIG_ will be taken in account when generating
> rte_config.h (see rte.sdkconfig.mk and scripts/gen-config-h.sh). But
> maybe it's not related to your issue.

Yes, Atleast build and check :-) Thanks a lot
>
> Regards,
> Olivier

^ permalink raw reply	[flat|nested] 14+ messages in thread

end of thread, other threads:[~2015-01-16 16:47 UTC | newest]

Thread overview: 14+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-12-24 13:26 [dpdk-dev] No probed ethernet devices /DPDP 1.7.1 in Fedora 21 sothy shan
2014-12-24 15:03 ` Masaru Oki
2014-12-24 15:04 ` Neil Horman
2014-12-25  9:11   ` sothy shan
2014-12-25 17:08     ` Neil Horman
2014-12-26  8:01       ` sothy shan
2014-12-26 14:37         ` Neil Horman
2015-01-09 16:20           ` sothy shan
2015-01-10 12:44             ` Neil Horman
2015-01-16 14:10               ` sothy shan
2015-01-16 14:27                 ` Olivier MATZ
2015-01-16 16:07                   ` sothy shan
2015-01-16 16:35                     ` Olivier MATZ
2015-01-16 16:47                       ` sothy shan

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git