DPDK usage discussions
 help / color / mirror / Atom feed
From: Paras Jha <dreadiscool@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] DPDK KNI with LACP
Date: Mon, 25 Jun 2018 13:44:23 -0700	[thread overview]
Message-ID: <CAMs8r4O=pLRZDbPU5AbNUZQ+=Vw8BNzJFOMMQeKc87ViNGTn6g@mail.gmail.com> (raw)

Hello all,

I'm running a Debian 9 system with 4x10G courtesy of  X710 card.

I have a small test running where traffic from the NIC is forwarded onto
KNI, and vice versa. This works without an issue.

However, if I try to set up a bond using these interfaces using the Linux
kernel itself (not the bonding PMD that DPDK provides) then on the router
side, the interface is marked as LACP-BLOCKED. Does anyone have any idea as
to why this may be happening?

Running tcpdump on the KNI shows that the LACP packets are indeed being
forwarded into the kernel, but I can't see any response from the kernel.
The same bond configuration works fine without DPDK's KNI.

Here's a hexdump snippet of the traffic that I'm seeing come through.

01 80 C2 00 00 02 00 0C DB FA D7 91 88 09 01 01 01 14 00 01 00 0C DB FA D7
00 00 64 00 01 00 92 4F 00 00 00 02 14 00 01 00 00 00 00 00 00 00 91 00 01
00 00 78 00 00 00 03 10 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

I'm aware that the LACP driver that exists within DPDK itself can be
utilized, but at this point I'm more curious as to what could be causing
this behavior, and if there are any gotchas that I am inadvertently missing

Many thanks in advance!

                 reply	other threads:[~2018-06-25 20:44 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAMs8r4O=pLRZDbPU5AbNUZQ+=Vw8BNzJFOMMQeKc87ViNGTn6g@mail.gmail.com' \
    --to=dreadiscool@gmail.com \
    --cc=users@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).