From: John Fastabend <john.fastabend@gmail.com>
To: Jiri Pirko <jiri@resnulli.us>
Cc: "Varlese, Marco" <marco.varlese@intel.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"stephen@networkplumber.org" <stephen@networkplumber.org>,
"Fastabend, John R" <john.r.fastabend@intel.com>,
"roopa@cumulusnetworks.com" <roopa@cumulusnetworks.com>,
"sfeldma@gmail.com" <sfeldma@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH net-next 1/1] net: Support for switch port configuration
Date: Wed, 10 Dec 2014 09:03:51 -0800 [thread overview]
Message-ID: <54887CF7.70708@gmail.com> (raw)
In-Reply-To: <20141210165018.GG1863@nanopsycho.orion>
On 12/10/2014 08:50 AM, Jiri Pirko wrote:
> Wed, Dec 10, 2014 at 05:23:40PM CET, marco.varlese@intel.com wrote:
>> From: Marco Varlese <marco.varlese@intel.com>
>>
>> Switch hardware offers a list of attributes that are configurable
>> on a per port basis.
>> This patch provides a mechanism to configure switch ports by adding
>> an NDO for setting specific values to specific attributes.
>> There will be a separate patch that extends iproute2 to call the
>> new NDO.
>
>
> What are these attributes? Can you give some examples. I'm asking
> because there is a plan to pass generic attributes to switch ports
> replacing current specific ndo_switch_port_stp_update. In this case,
> bridge is setting that attribute.
>
> Is there need to set something directly from userspace or does it make
> rather sense to use involved bridge/ovs/bond ? I think that both will be
> needed.
+1
I think for many attributes it would be best to have both. The in
kernel callers and netlink userspace can use the same driver ndo_ops.
But then we don't _require_ any specific bridge/ovs/etc module. And we
may have some attributes that are not specific to any existing software
module. I'm guessing Marco has some examples of these.
[...]
--
John Fastabend Intel Corporation
next prev parent reply other threads:[~2014-12-10 17:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-10 16:23 [RFC PATCH net-next 1/1] net: Support for switch port configuration Varlese, Marco
2014-12-10 16:50 ` Jiri Pirko
2014-12-10 17:03 ` John Fastabend [this message]
2014-12-11 9:59 ` Varlese, Marco
2014-12-11 11:01 ` Jiri Pirko
2014-12-11 12:02 ` Varlese, Marco
2014-12-11 13:08 ` Jiri Pirko
2014-12-11 13:55 ` Varlese, Marco
2014-12-11 16:37 ` Roopa Prabhu
2014-12-11 16:56 ` Jiri Pirko
2014-12-11 17:41 ` Roopa Prabhu
2014-12-11 17:54 ` Jiri Pirko
2014-12-11 17:55 ` John Fastabend
2014-12-12 9:19 ` Varlese, Marco
2014-12-13 7:06 ` Roopa Prabhu
2014-12-15 9:39 ` Varlese, Marco
2014-12-15 10:58 ` Arad, Ronen
2014-12-15 16:18 ` Roopa Prabhu
2014-12-13 14:39 ` Rosen, Rami
2014-12-15 14:07 ` Thomas Graf
2014-12-15 14:29 ` Varlese, Marco
2014-12-15 14:40 ` Thomas Graf
2014-12-15 16:44 ` Roopa Prabhu
2014-12-15 14:05 ` Thomas Graf
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=54887CF7.70708@gmail.com \
--to=john.fastabend@gmail.com \
--cc=jiri@resnulli.us \
--cc=john.r.fastabend@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.varlese@intel.com \
--cc=netdev@vger.kernel.org \
--cc=roopa@cumulusnetworks.com \
--cc=sfeldma@gmail.com \
--cc=stephen@networkplumber.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).