I am using the dpdk1.6.0r1
I could not find a complete clarification, sorry if missed.
VMXNET3 PMD
I have enabled the VMXNET3 PMD in the dpdk.
# Compile burst-oriented VMXNET3 PMD driver
#
CONFIG_RTE_LIBRTE_VMXNET3_PMD=y
CONFIG_RTE_LIBRTE_VMXNET3_DEBUG_INIT=y
CONFIG_RTE_LIBRTE_VMXN
t features from all of them and maintain one copy. I'm sure
> that developers contributing from VMware would also support that idea
> because then it makes easy to maintain and debug and bug fix and most
> importantly avoid such confusion in future.
>
> Thanks,
> Rashmin
>
&g
e, dlerror());
// RTE_LOG(WARNING, EAL, "%s\n", dlerror());
}
On Tue, Nov 11, 2014 at 9:19 AM, Patel, Rashmin N wrote:
> Please find comments in-lined.
>
>
>
> Thanks,
>
> RP
>
>
>
> *From:* Aziz Hajee [mailto:aziz at saisei.com]
RX bytes:3186 (3.1 KB) TX bytes:0 (0.0 B)
On Mon, Jan 12, 2015 at 3:24 AM, Bruce Richardson <
bruce.richardson at intel.com> wrote:
> On Fri, Jan 09, 2015 at 05:20:26PM -0800, Aziz Hajee wrote:
> > I am using the dpdk1.6.0r1
> > The rte_kni.lo is loaded:
> > lsmod |
I am using the dpdk1.6.0r1
The rte_kni.lo is loaded:
lsmod | grep kni
rte_kni 279134 1
however, the ifconfig vEth0, and vEth1 does not show link up ?
How do i get the operational state up for these interfaces.
$ sudo tcpdump -i vEth0
tcpdump: vEth0: That device is not up
ifconfig v
5 matches
Mail list logo