DPDK usage discussions
 help / color / mirror / Atom feed
From: Eugene Iskra <eugenei@saguna.net>
To: users@dpdk.org
Subject: [dpdk-users] bonding - slave mac address is not updated
Date: Mon, 7 Oct 2019 21:17:15 +0300	[thread overview]
Message-ID: <4ed5ac6c-046e-fc70-f756-e86fdaa16423@saguna.net> (raw)

Hello,

I am using DPDK 18.11.2 with bonding in BONDING_MODE_ACTIVE_BACKUP mode.
When both slaves are connected to the switch, the primary slave receives 
/ sends traffic
and everything work well.
When the primary port is disconnected, and the secondary slave becomes 
primary,
no packets are received, except for broadcast packets.

Looking at bond_ethdev_lsc_event_callback in rte_eth_bond_pmd.c, I see that
mac_address_slaves_update is called only when slave link is brought up, 
but if slave
goes down, mac addresses are not updated.

Also the mac_address_slaves_update function itself doesn't seem to 
update mac address
correctly for the new primary port, since it updates 
internals->primary_port instead
of internals->current_primary_port.

Is this an actual bug or am I misunderstanding something / something is 
not configured
right?


Regards,
Eugene

             reply	other threads:[~2019-10-07 18:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-10-07 18:17 Eugene Iskra [this message]
2019-10-10  8:34 ` Eugene Iskra

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=4ed5ac6c-046e-fc70-f756-e86fdaa16423@saguna.net \
    --to=eugenei@saguna.net \
    --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).