[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1504821112.2117.8.camel@intel.com>
Date: Thu, 7 Sep 2017 21:51:53 +0000
From: "Guedes, Andre" <andre.guedes@...el.com>
To: "richardcochran@...il.com" <richardcochran@...il.com>,
"henrik@...tad.us" <henrik@...tad.us>
CC: "jiri@...nulli.us" <jiri@...nulli.us>,
"jhs@...atatu.com" <jhs@...atatu.com>,
"Ong, Boon Leong" <boon.leong.ong@...el.com>,
"xiyou.wangcong@...il.com" <xiyou.wangcong@...il.com>,
"Gomes, Vinicius" <vinicius.gomes@...el.com>,
"Sanchez-Palencia, Jesus" <jesus.sanchez-palencia@...el.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"Briano, Ivan" <ivan.briano@...el.com>,
"intel-wired-lan@...ts.osuosl.org" <intel-wired-lan@...ts.osuosl.org>
Subject: Re: [RFC net-next 0/5] TSN: Add qdisc-based config interfaces for
traffic shapers
On Thu, 2017-09-07 at 18:18 +0200, Henrik Austad wrote:
> On Thu, Sep 07, 2017 at 05:53:15PM +0200, Richard Cochran wrote:
> > On Thu, Sep 07, 2017 at 05:27:51PM +0200, Henrik Austad wrote:
> > > On Thu, Sep 07, 2017 at 02:40:18PM +0200, Richard Cochran wrote:
> > > And if you want to this driver to act as a bridge, how do you accomodate
> > > change in network requirements? (i.e. how does this work with switchdev?)
> >
> > To my understanding, this Qdisc idea provides QoS for the host's
> > transmitted traffic, and nothing more.
>
> Ok, then we're on the same page.
>
> > > - Or am I overthinking this?
> >
> > Being able to configure the external ports of a switchdev is probably
> > a nice feature, but that is another story. (But maybe I misunderstood
> > the authors' intent!)
>
> ok, chalk that one up for later perhaps
Just to clarify, we've been most focused on end-station use-cases. We've
considered some bridge use-cases as well just to verify that the proposed
design won't be an issue if someone else goes for it.
- Andre
Download attachment "smime.p7s" of type "application/x-pkcs7-signature" (3262 bytes)
Powered by blists - more mailing lists