From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from shards.monkeyblade.net ([184.105.139.130]:43156 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751541AbeCWQRt (ORCPT ); Fri, 23 Mar 2018 12:17:49 -0400 Date: Fri, 23 Mar 2018 12:17:47 -0400 (EDT) Message-Id: <20180323.121747.2120157916968005999.davem@davemloft.net> To: 3chas3@gmail.com Cc: netdev@vger.kernel.org, stephen@networkplumber.org Subject: Re: [PATCH net-next] bridge: Allow max MTU when multiple VLANs present From: David Miller In-Reply-To: <20180322153406.17760-1-3chas3@gmail.com> References: <20180322153406.17760-1-3chas3@gmail.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: netdev-owner@vger.kernel.org List-ID: From: Chas Williams <3chas3@gmail.com> Date: Thu, 22 Mar 2018 11:34:06 -0400 > If the bridge is allowing multiple VLANs, some VLANs may have > different MTUs. Instead of choosing the minimum MTU for the > bridge interface, choose the maximum MTU of the bridge members. > With this the user only needs to set a larger MTU on the member > ports that are participating in the large MTU VLANS. > > Signed-off-by: Chas Williams <3chas3@gmail.com> Applied, thanks.