From: Stephen Hemminger <shemminger@vyatta.com>
To: Jiri Pirko <jpirko@redhat.com>
Cc: netdev@vger.kernel.org, shemminger@linux-foundation.org,
bridge@lists.linux-foundation.org, davem@davemloft.net
Subject: Re: [patch net-next-2.6] bridge: allow hub-like behaviour
Date: Thu, 12 Aug 2010 08:55:20 -0400 [thread overview]
Message-ID: <20100812085520.4f56ebe6@s6510> (raw)
In-Reply-To: <20100812124847.GD3115@psychotron.brq.redhat.com>
On Thu, 12 Aug 2010 14:48:48 +0200
Jiri Pirko <jpirko@redhat.com> wrote:
> Thu, Aug 12, 2010 at 02:35:41PM CEST, shemminger@vyatta.com wrote:
> >On Thu, 12 Aug 2010 13:15:24 +0200
> >Jiri Pirko <jpirko@redhat.com> wrote:
> >
> >> Wed, Aug 11, 2010 at 06:07:41PM CEST, shemminger@vyatta.com wrote:
> >> >NO. unnecessary
> >> >
> >> >Already possible, without patch. Just set the hold time
> >> >on the bridge to 0!
> >>
> >> Sorry, but could you please point me a sysfs node where should I do this
> >> setting? Unable to find this.
> >>
> >> Thanks.
> >>
> >
> >/sys/class/net/ethX/brport/hold_timer
>
> That's read-only:
>
> static BRPORT_ATTR(hold_timer, S_IRUGO, show_hold_timer, NULL);
>
Guess you have to use ioctl() interface to change it for now.
Looks like a missed opportunity when sysfs support was added.
There are some other values like forward_delay that have same problem.
next prev parent reply other threads:[~2010-08-12 12:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-11 14:40 [patch net-next-2.6] bridge: allow hub-like behaviour Jiri Pirko
2010-08-11 16:07 ` Stephen Hemminger
2010-08-12 11:15 ` Jiri Pirko
2010-08-12 12:35 ` Stephen Hemminger
2010-08-12 12:48 ` Jiri Pirko
2010-08-12 12:55 ` Stephen Hemminger [this message]
2010-08-12 13:20 ` Jiri Pirko
2010-08-12 13:02 ` Stephen Hemminger
2010-08-12 13:40 ` Jiri Pirko
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=20100812085520.4f56ebe6@s6510 \
--to=shemminger@vyatta.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=jpirko@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=shemminger@linux-foundation.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).