From: "David S. Miller" <davem@davemloft.net>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com, bridge@lists.osdl.org
Subject: Re: [PATCH] bridge: no update when hold time is zero
Date: Mon, 14 Mar 2005 21:40:22 -0800 [thread overview]
Message-ID: <20050314214022.623ff3b0.davem@davemloft.net> (raw)
In-Reply-To: <20050311102636.30934f12@dxpl.pdx.osdl.net>
On Fri, 11 Mar 2005 10:26:36 -0800
Stephen Hemminger <shemminger@osdl.org> wrote:
> Some users, set hold time to zero on bridge so it always does
> flooding. This is usually when using it with wireless. The new RCU
> based code changed the behaviour so the bridge would not flood for
> one GC interval. This patch restores the original behaviour.
Applied, thanks Stephen.
Please don't forget the signed-off-by line next time :-)
prev parent reply other threads:[~2005-03-15 5:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 23:44 [PATCH] (4/4) bridge: forwarding table lockless update Stephen Hemminger
2005-03-11 2:51 ` David S. Miller
2005-03-11 18:26 ` [PATCH] bridge: no update when hold time is zero Stephen Hemminger
2005-03-15 5:40 ` David S. Miller [this message]
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=20050314214022.623ff3b0.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bridge@lists.osdl.org \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/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).