From: Andrew Lunn <andrew@lunn.ch>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: sfeldma@gmail.com, netdev@vger.kernel.org, jiri@resnulli.us,
siva.mannem.lnx@gmail.com, pjonnala@broadcom.com,
stephen@networkplumber.org, roopa@cumulusnetworks.com,
vivien.didelot@savoirfairelinux.com
Subject: Re: [PATCH net-next 0/4] switchdev: push bridge attributes down
Date: Fri, 25 Sep 2015 03:53:05 +0200 [thread overview]
Message-ID: <20150925015305.GA25275@lunn.ch> (raw)
In-Reply-To: <5604A208.3030902@gmail.com>
> So, without a better device to hold that kind of information (in the
> future it could be a global, switch-specific device holding that
> information), I agree with your decision to take the bridge device to
> hold that attribute, it still feels a bit uncomfortable to have
> switchdev_attr_port() take a bridge device parameter, but whatever, here
> is a scenario I am wondering how we would want to proceed with:
>
> - suppose we have a switch which is only able to control ageing
> globally, not per port or any other kind of logical domain
Marvell switches only have global ageing settings, and it has to be a
multiple of 15 seconds, from 0 to 3825 seconds.
Andrew
next prev parent reply other threads:[~2015-09-25 2:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 20:59 [PATCH net-next 0/4] switchdev: push bridge attributes down sfeldma
2015-09-24 20:59 ` [PATCH net-next 1/4] switchdev: add bridge attributes sfeldma
2015-09-25 4:32 ` Premkumar Jonnala
2015-09-25 5:51 ` David Miller
2015-09-24 20:59 ` [PATCH net-next 2/4] switchdev: skip over ports returning -EOPNOTSUPP when recursing ports sfeldma
2015-09-25 4:33 ` Premkumar Jonnala
2015-09-24 20:59 ` [PATCH net-next 3/4] bridge: push bridge setting ageing_time down to switchdev sfeldma
2015-09-24 20:59 ` [PATCH net-next 4/4] rocker: handle setting bridge ageing_time sfeldma
2015-09-24 21:05 ` [PATCH net-next 0/4] switchdev: push bridge attributes down Stephen Hemminger
2015-09-25 3:25 ` Scott Feldman
2015-09-25 3:47 ` Stephen Hemminger
2015-09-25 1:23 ` Florian Fainelli
2015-09-25 1:53 ` Andrew Lunn [this message]
2015-09-25 4:26 ` Scott Feldman
2015-09-29 5:22 ` Florian Fainelli
2015-09-29 5:07 ` David Miller
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=20150925015305.GA25275@lunn.ch \
--to=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=jiri@resnulli.us \
--cc=netdev@vger.kernel.org \
--cc=pjonnala@broadcom.com \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@gmail.com \
--cc=siva.mannem.lnx@gmail.com \
--cc=stephen@networkplumber.org \
--cc=vivien.didelot@savoirfairelinux.com \
/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).