[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <52F45EED.4020108@huawei.com>
Date: Fri, 7 Feb 2014 12:19:57 +0800
From: Ding Tianhong <dingtianhong@...wei.com>
To: David Miller <davem@...emloft.net>
CC: <fubar@...ibm.com>, <vfalico@...hat.com>, <andy@...yhouse.net>,
<netdev@...r.kernel.org>
Subject: Re: [PATCH RESEND net-next] bonding: don't permit slaves to change
their mtu independently
On 2014/2/2 8:53, David Miller wrote:
> From: Ding Tianhong <dingtianhong@...wei.com>
> Date: Sat, 25 Jan 2014 12:55:09 +0800
>
>> I have come to a conclusion by testing all modes for mtu changing:
>>
>> 1). If the slaves support changing mtu and no need to restart the device,
>> just like virtual nic, the master will not lost any packages for all
>> mode.
>>
>> 2). If the slaves support changing mtu and need to restart the device,
>> just like Intel 82599, the AB, 802.3, ALB and TLB mode may lost
>> packages, but other modes could work well.
>>
>> The reason is that when the slave's mtu has been changed, the slave's hw will
>> restart, if the slave is current active slave, the master may set the
>> slave to backup state and reselect a new slave, after the reselect processing,
>> the master could work again, but if in load-balance mode, the master could
>> select another active slave to send and recv packages.
>>
>> So the best way to fix the problem is don't permit slave to change their
>> mtu independently.
>>
>> Cc: Jay Vosburgh <fubar@...ibm.com>
>> Cc: Veaceslav Falico <vfalico@...hat.com>
>> Cc: Andy Gospodarek <andy@...yhouse.net>
>> Signed-off-by: Ding Tianhong <dingtianhong@...wei.com>
>
> This has been rotting in patchwork for a week, and desperately needs
> someone to review it.
>
>
Self Naked, this patch did not consider the bond dev MTU changing, because
if I forbidden the slave to change mtu in any way, the bond will not change
its own mtu anymore, so I should think more about this situation. Sorry for the
noise.
Regards
Ding
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists