Hello,
I've recently migrated from dpdk-18.05 to dpdk-20.11. I built "kni"
example according to this tutorial [1 [1]], every thing is fine except
that
it has no output packet (no tx). have I ignored something? I would be
grateful if anyone could help me.
It may also be helpful to mention that a
Hello,
I've recently migrated from dpdk-18.05 to dpdk-20.11. I built "kni"
example according to this tutorial [1], every thing is fine except that
it has no output packet (no tx). have I ignored something? I would be
grateful if anyone could help me.
outputs:
> ./BUILD/KNI -L 4-7 -N 4 -- -P -
Calling rte_eth_allmulticast_enable() in the DPDK KNI sample app
solved the issue. Sharing the fix so that it will be helpful for
others facing similar issue.
Regards,
Srini
/dpdk-stable-18.08.1/examples/kni/main.c
@@ -618,8 +619,10 @@
rte_exit(EXIT_FAILURE, "Could not start port
On further investigation, it' seen that the dvSwitch does not have any
multicast MAC registered when using DPDK vmxnet3 poll mode driver
along with the KNI sample app post configuring IPv6 address on the
vEth0 KNI interface. The same interface when used with the kernel
driver works fine. Any help o
Hi,
I observed that DPDK kni interface is not able to receive solicited
node multicast addressed (derived from the IPv6 address configured on
vEth0 interface) when the kni sample app is being run in Ubuntu VM on
ESXI server. The only way to have the frames reach the kni interface
is by setting t
Hi,
I am running KNI example.
Once I run KNI, a virtual interface is created and I assign an IP to it.
After a few minutes the IP address is gone, ( I assume the interface would have
flapped).
This issue is seen in random. Can anyone help me out in debugging this issue
further.
Thanks,
Prashan
Hi Robert,
Thanks a lot, it fixed the issue.
Regards
Venkat
On 30 April 2015 at 20:11, Sanford, Robert wrote:
> Hi Venkat,
>
> Perhaps your DPDK application needs to slow-poll KNI devices via
> rte_kni_handle_request( ).
>
> http://dpdk.org/doc/api/rte__kni_8h.html
>
> --
> Regards,
> Robert
>
Hi,
I am testing DPDK 2.0 release.
I am not able to bring the KNI interface up.
It always gives the following error.
SIOCSIFFLAGS: Timer expired
This is on Ubuntu,
Linux vthummala-PowerEdge-R720 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10
19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
Please
Hi Venkat,
Perhaps your DPDK application needs to slow-poll KNI devices via
rte_kni_handle_request( ).
http://dpdk.org/doc/api/rte__kni_8h.html
--
Regards,
Robert
>Hi,
>
>I am testing DPDK 2.0 release.
>I am not able to bring the KNI interface up.
>It always gives the following error.
>
>SIOCS
Yes, the DPDK reports port is UP.
By the following change in the registered callback function to comment out
stop/start the dpdk interface, I can bring the KNI vEthX interfaces up:
(I guess, the reason is the ret value is now the default ret = 0, and no
error from stop/start. )
kni_config_network_
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 | 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.
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
rototype under development might fit whatever you
requirement, or you can
integrate commercial or open-sourced user space TCP/IP stack.
>
> >
> >> -Original Message-
> >> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Harish Patil
> >> Sent: Sat
modules, to achieve full networking stack functionality at
least in a non-virtualized environment ?
>
>> -Original Message-
>> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Harish Patil
>> Sent: Saturday, July 19, 2014 8:09 AM
>> To: dev at dpdk.org
>> Subj
space still process fast path packets.
> -Original Message-
> From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Harish Patil
> Sent: Saturday, July 19, 2014 8:09 AM
> To: dev at dpdk.org
> Subject: [dpdk-dev] KNI interface
>
> Hello dpdk-dev,
> Went thru? cou
Hello dpdk-dev,
Went thru? couple of documentation but not very clear to me. Does using
KNI means handing over all the packets received/transmitted by the poll
mode driver to the linux stack or can it be controlled for the control
packets only ? What is the KNI use-case (besides ethtool) and what a
On Sat, Jul 19, 2014 at 12:08:35AM +, Harish Patil wrote:
> Hello dpdk-dev,
> Went thru? couple of documentation but not very clear to me. Does using
> KNI means handing over all the packets received/transmitted by the poll
> mode driver to the linux stack or can it be controlled for the contro
17 matches
Mail list logo
