Hi,
I can't find a MACRO for this nic in rte_pci_dev_ids.h, does this mean this
isn't supported as of this moment ?
I only saw MACROS for x540t and x540t1.
Cheers
Pepe
--
To stop learning is like to stop loving.
23/12/2013 10:18, Jose Gavine Cueto :
> I can't find a MACRO for this nic in rte_pci_dev_ids.h, does this mean this
> isn't supported as of this moment ?
Yes
But probably that
hw->mac.type = ixgbe_mac_X540
apply also to x540-at2.
Please to try to add it and send the patch if it works.
--
Sorry I accidentally excluded the list. I've pasted the replies:
---
I see thanks.
I'm actually running my DPDK application on a guest OS but I'm always
getting an invalid ins
Thanks again. So there is a possibility that vf will fail with DPDK due to
not fully supported pf. Please correct me if I'm wrong.
Cheers,
Pepe
On Fri, Jan 3, 2014 at 5:09 PM, Jose Gavine Cueto wrote:
> Sorry I accidentally excluded the list. I've pasted the replies:
>
>
>
>
03/01/2014 10:16, Jose Gavine Cueto :
> Thanks again. So there is a possibility that vf will fail with DPDK due to
> not fully supported pf. Please correct me if I'm wrong.
Please Jose, better describe your use case in order to have the right answer.
The standard SR-IOV use case is to use a rec
Hi Thomas,
I thought I was clear enough, sorry for the confusion.
I am running a DPDK application in a guest VM which uses one VF. This VM
runs on top of the host that has an x540-at2 NIC and uses the ixgbe driver.
The issue was that every time I run the DPDK application in the VM it
errors an
03/01/2014 11:09, Jose Gavine Cueto :
> I am running a DPDK application in a guest VM which uses one VF. This VM
> runs on top of the host that has an x540-at2 NIC and uses the ixgbe driver.
> The issue was that every time I run the DPDK application in the VM it
> errors an invalid instruction an
I haven't added it yet, because as of the moment I do not have an access to
the built DPDK library I was using. I was just linking it with my DPDK
application.
I tried to debug it with GDB and disassembled it, the invalid instruction
was "vzeroupper" which occurs at rte_eal_init, somewhere when i
Pepe ,
Was the DPDK library compiled on a different machine and the used in the VM? It
looks like it has been compiled for native AVX (hence the vzeroupper). Could
you dump cpuinfo in the VM and see what instruction set the VM supports?
-Venky
Sent from my iPhone
> On Jan 3, 2014, at 2:32
03/01/2014 13:43, Venkatesan, Venky :
> "Jose Gavine Cueto" wrote:
> > I tried to debug it with GDB and disassembled it, the invalid instruction
> > was "vzeroupper" which occurs at rte_eal_init, somewhere when initializing
> > pthreads.
> Was the DPDK library compiled on a different machine and
Hi Venky,
On Fri, Jan 3, 2014 at 9:43 PM, Venkatesan, Venky <
venky.venkatesan at intel.com> wrote:
> Pepe ,
>
> Was the DPDK library compiled on a different machine and the used in the
> VM? It looks like it has been compiled for native AVX (hence the
> vzeroupper). Could you dump cpuinfo in th
05/01/2014 22:31, Jose Gavine Cueto :
> venky.venkatesan at intel.com> wrote:
> > Was the DPDK library compiled on a different machine and the used in the
> > VM? It looks like it has been compiled for native AVX (hence the
> > vzeroupper). Could you dump cpuinfo in the VM and see what instruction
Hi Thomas,
On Sun, Jan 5, 2014 at 10:54 PM, Thomas Monjalon
wrote:
> 05/01/2014 22:31, Jose Gavine Cueto :
> > venky.venkatesan at intel.com> wrote:
> > > Was the DPDK library compiled on a different machine and the used in
> the
> > > VM? It looks like it has been compiled for native AVX (hence
Hi,
Just to let you know that the invalid instruction error above went away
when AVX was enabled using host model cpu mode in the VM.
Thanks,
Pepe
On Mon, Jan 6, 2014 at 2:03 PM, Jose Gavine Cueto wrote:
> Hi Thomas,
>
> On Sun, Jan 5, 2014 at 10:54 PM, Thomas Monjalon <
> thomas.monjalon at 6
14 matches
Mail list logo
