[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20140206.194107.170476650427156102.davem@davemloft.net>
Date: Thu, 06 Feb 2014 19:41:07 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: dingtianhong@...wei.com
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
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>
Without any review, I'm not applying this patch, sorry.
--
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