From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <4D73CC04.6060909@computer.org> Date: Sun, 06 Mar 2011 19:01:40 +0100 From: Jan Ceuleers MIME-Version: 1.0 References: <20110306051833.GA3098@mira.lan.galacticasoftware.com> <1154832100.13939.1299393783798.JavaMail.root@tahiti.vyatta.com> <20110306080328.GA3850@mira.lan.galacticasoftware.com> In-Reply-To: <20110306080328.GA3850@mira.lan.galacticasoftware.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Bridge] [PATCH 1/2] Issue NETDEV_CHANGE notification when bridge changes state List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Adam Majer Cc: "Pekka Savola (ipv6)" , Hideaki YOSHIFUJI , netdev@vger.kernel.org, bridge@lists.linux-foundation.org, James Morris , Stephen Hemminger , Alexey Kuznetsov , "David S. Miller" On 06/03/11 09:03, Adam Majer wrote: > On Sat, Mar 05, 2011 at 10:43:03PM -0800, Stephen Hemminger wrote: >> Why not set forwarding delay to zero? I don't think you are using STP? > > No, I'm not relying on STP. I think setting learning->forwarding delay > to 0 could cause problems with STP like loops until the loop is > detected. I don't think that Stephen is saying that you should hard-code the forwarding delay as zero (i.e. to remove the delay from the kernel completely), but rather use brctl to set the forwarding delay to zero on bridge instances in which you're not using STP. HTH, Jan