DPDK usage discussions
 help / color / mirror / Atom feed
From: Vincent Li <vincent.mc.li@gmail.com>
To: users@dpdk.org
Cc: dev@dpdk.org
Subject: [dpdk-users] Pktgen DPDK net bonding mode 4 802.3AD (LACP) not working with BIGIP trunk with LACP enabled
Date: Wed, 11 Jan 2017 10:08:19 -0800	[thread overview]
Message-ID: <CAK3+h2xzFvAaWFUrh_LyTgk7Sju_k2oxT_5Yg4ELo81NE3sUEA@mail.gmail.com> (raw)

Hi,

I have direct two cable connections between Pktgen DPDK box and BIGIP

this is a problem I am not sure if it Pktgen, or the DPDK net bonding mode
4 LACP, or the BIGIP trunk with LACP enabled issue, I am hoping someone
here have more clue and give me some direction on how to trouble shoot
this. I am suspecting there might some issue between DPDK net bonding
8023ad mode 4 and BIGIP trunk LACP mode. I turned
on CONFIG_RTE_LOG_LEVEL=RTE_LOG_DEBUG and
defined RTE_LIBRTE_BOND_DEBUG_8023AD
in drivers/net/bonding/rte_eth_bond_8023ad.c hoping getting more debug
output in Pktgen, I could not see any debug output for 8023ad protocol.


packet tx/rx works :

1 Pktgen with DPDK net bonding mode 1, 2, 3, 5
2 BIGIP trunk with LACP disabled (trunk port status UP)

packet tx/rx failed:

1, Pktgen with DPDK net bonding mode 4 802.3AD
2, BIGIP trunk with LACP enabled (trunk status is DOWN)

or
1, Pktgen with DPDK net bonding mode 4 802.3AD
2, BIGIP trunk with LACP disabled (trunk status is UP)

my end goal is to achieve 10G < througput < 20G with Pktgen DPDK net
bonding with Intel 82599 to load test BIGIP, so far with bonding mode 1,
2,3, 5, I am unable to achieve throughput > 10G.

             reply	other threads:[~2017-01-11 18:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-11 18:08 Vincent Li [this message]
2017-01-11 18:51 ` Wiles, Keith
2017-01-11 19:08   ` Vincent Li

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=CAK3+h2xzFvAaWFUrh_LyTgk7Sju_k2oxT_5Yg4ELo81NE3sUEA@mail.gmail.com \
    --to=vincent.mc.li@gmail.com \
    --cc=dev@dpdk.org \
    --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).