DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Min Hu (Connor)" <humin29@huawei.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: Declan Doherty <declan.doherty@intel.com>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] Question about bonding port promiscuous
Date: Thu, 21 Oct 2021 21:39:46 +0800	[thread overview]
Message-ID: <a26d12fc-01d9-d818-c4a5-d0da25d7fee2@huawei.com> (raw)
In-Reply-To: <6cd232ec-3683-6774-38b1-c26230d989c9@huawei.com>

Hi, David,
	how about your opinion ?

在 2021/10/21 20:58, Min Hu (Connor) 写道:
> Hi, Ferruh, Thomas,
>      any comments?
> 
> 在 2021/10/19 19:52, Min Hu (Connor) 写道:
>> Hi, anyone could give me a reply? thanks.
>>
>> 在 2021/10/14 10:13, Min Hu (Connor) 写道:
>>> Hi, Declan Doherty,
>>>      In function "bond_ethdev_promiscuous_disable",
>>> for "ROUND ROBIN","BALANCE","BROADCAST","8023AD" mode, Promiscuous mode
>>> is propagated to all slaves.
>>>
>>> While for "ACTIVE_BACKUP", "TLB", "ALB", promiscuous mode is 
>>> propagated only to primary slave.
>>>
>>> Why?
>>>
>>> The second question, for "ACTIVE_BACKUP", when primary active slave
>>> fails, a different slave becomes active, does the promiscuous mode state
>>> of former primary should be set to the new primary?
>>>
>>>      Hope for your reply.
>>>      Best Wishes.
>>> .
>> .
> .

  reply	other threads:[~2021-10-21 13:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14  2:13 Min Hu (Connor)
2021-10-19 11:52 ` Min Hu (Connor)
2021-10-21 12:58   ` Min Hu (Connor)
2021-10-21 13:39     ` Min Hu (Connor) [this message]
2021-10-27  3:21 Min Hu (Connor)
2021-10-27 13:47 ` David Marchand
2021-10-28  2:08   ` Min Hu (Connor)

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=a26d12fc-01d9-d818-c4a5-d0da25d7fee2@huawei.com \
    --to=humin29@huawei.com \
    --cc=david.marchand@redhat.com \
    --cc=declan.doherty@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=thomas@monjalon.net \
    /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).