All of lore.kernel.org
 help / color / mirror / Atom feed
From: Guedes, Andre <andre.guedes@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [RFC net-next 0/5] TSN: Add qdisc-based config interfaces for traffic shapers
Date: Thu, 7 Sep 2017 21:51:53 +0000	[thread overview]
Message-ID: <1504821112.2117.8.camel@intel.com> (raw)
In-Reply-To: <20170907161838.GB9064@sisyphus.home.austad.us>

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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3262 bytes
Desc: not available
URL: <http://lists.osuosl.org/pipermail/intel-wired-lan/attachments/20170907/83455e39/attachment-0001.bin>

WARNING: multiple messages have this Message-ID (diff)
From: "Guedes, Andre" <andre.guedes@intel.com>
To: "richardcochran@gmail.com" <richardcochran@gmail.com>,
	"henrik@austad.us" <henrik@austad.us>
Cc: "jiri@resnulli.us" <jiri@resnulli.us>,
	"jhs@mojatatu.com" <jhs@mojatatu.com>,
	"Ong, Boon Leong" <boon.leong.ong@intel.com>,
	"xiyou.wangcong@gmail.com" <xiyou.wangcong@gmail.com>,
	"Gomes, Vinicius" <vinicius.gomes@intel.com>,
	"Sanchez-Palencia, Jesus" <jesus.sanchez-palencia@intel.com>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"Briano, Ivan" <ivan.briano@intel.com>,
	"intel-wired-lan@lists.osuosl.org"
	<intel-wired-lan@lists.osuosl.org>
Subject: Re: [RFC net-next 0/5] TSN: Add qdisc-based config interfaces for traffic shapers
Date: Thu, 7 Sep 2017 21:51:53 +0000	[thread overview]
Message-ID: <1504821112.2117.8.camel@intel.com> (raw)
In-Reply-To: <20170907161838.GB9064@sisyphus.home.austad.us>

[-- Attachment #1: Type: text/plain, Size: 1077 bytes --]

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

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 3262 bytes --]

  reply	other threads:[~2017-09-07 21:51 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-01  1:26 [Intel-wired-lan] [RFC net-next 0/5] TSN: Add qdisc-based config interfaces for traffic shapers Vinicius Costa Gomes
2017-09-01  1:26 ` Vinicius Costa Gomes
2017-09-01  1:26 ` [Intel-wired-lan] [RFC net-next 1/5] net/sched: Introduce the user API for the CBS shaper Vinicius Costa Gomes
2017-09-01  1:26   ` Vinicius Costa Gomes
2017-09-01  1:26 ` [Intel-wired-lan] [RFC net-next 2/5] net/sched: Introduce Credit Based Shaper (CBS) qdisc Vinicius Costa Gomes
2017-09-01  1:26   ` Vinicius Costa Gomes
2017-09-08 13:43   ` [Intel-wired-lan] " Henrik Austad
2017-09-08 13:43     ` Henrik Austad
2017-09-14  0:39     ` [Intel-wired-lan] " Vinicius Costa Gomes
2017-09-14  0:39       ` Vinicius Costa Gomes
2017-09-01  1:26 ` [Intel-wired-lan] [RFC net-next 3/5] igb: Add support for CBS offload Vinicius Costa Gomes
2017-09-01  1:26   ` Vinicius Costa Gomes
2017-09-01  1:26 ` [Intel-wired-lan] [RFC net-next 4/5] sample: Add TSN Talker and Listener examples Vinicius Costa Gomes
2017-09-01  1:26   ` Vinicius Costa Gomes
2017-09-01  1:26 ` [Intel-wired-lan] [RFC net-next 5/5] samples/tsn: Add script for calculating CBS config Vinicius Costa Gomes
2017-09-01  1:26   ` Vinicius Costa Gomes
2017-09-01 13:03 ` [Intel-wired-lan] [RFC net-next 0/5] TSN: Add qdisc-based config interfaces for traffic shapers Richard Cochran
2017-09-01 13:03   ` Richard Cochran
2017-09-01 16:12   ` [Intel-wired-lan] " Jesus Sanchez-Palencia
2017-09-01 16:12     ` Jesus Sanchez-Palencia
2017-09-01 16:53     ` [Intel-wired-lan] " Richard Cochran
2017-09-01 16:53       ` Richard Cochran
2017-09-05  7:20     ` [Intel-wired-lan] " Richard Cochran
2017-09-05  7:20       ` Richard Cochran
2017-09-07  5:34 ` [Intel-wired-lan] " Henrik Austad
2017-09-07  5:34   ` Henrik Austad
2017-09-07 12:40   ` [Intel-wired-lan] " Richard Cochran
2017-09-07 12:40     ` Richard Cochran
2017-09-07 15:27     ` [Intel-wired-lan] " Henrik Austad
2017-09-07 15:27       ` Henrik Austad
2017-09-07 15:53       ` [Intel-wired-lan] " Richard Cochran
2017-09-07 15:53         ` Richard Cochran
2017-09-07 16:18         ` [Intel-wired-lan] " Henrik Austad
2017-09-07 16:18           ` Henrik Austad
2017-09-07 21:51           ` Guedes, Andre [this message]
2017-09-07 21:51             ` Guedes, Andre
2017-09-07 19:58   ` [Intel-wired-lan] " Guedes, Andre
2017-09-07 19:58     ` Guedes, Andre
2017-09-08  6:06     ` [Intel-wired-lan] " Henrik Austad
2017-09-08  6:06       ` Henrik Austad
2017-09-08  1:29   ` [Intel-wired-lan] " Vinicius Costa Gomes
2017-09-08  1:29     ` Vinicius Costa Gomes
2017-09-12  4:56     ` [Intel-wired-lan] " Richard Cochran
2017-09-12  4:56       ` Richard Cochran
2017-09-18  8:02 ` [Intel-wired-lan] " Richard Cochran
2017-09-18  8:02   ` Richard Cochran
2017-09-18 11:46   ` [Intel-wired-lan] " Henrik Austad
2017-09-18 11:46     ` Henrik Austad
2017-09-18 23:06   ` [Intel-wired-lan] " Vinicius Costa Gomes
2017-09-18 23:06     ` Vinicius Costa Gomes
2017-09-19  5:22     ` [Intel-wired-lan] " Richard Cochran
2017-09-19  5:22       ` Richard Cochran
2017-09-19 13:14       ` [Intel-wired-lan] " Henrik Austad
2017-09-19 13:14         ` Henrik Austad
2017-09-20  0:19       ` [Intel-wired-lan] " Vinicius Costa Gomes
2017-09-20  0:19         ` Vinicius Costa Gomes
2017-09-20  5:25         ` [Intel-wired-lan] " Richard Cochran
2017-09-20  5:25           ` Richard Cochran
2017-10-18 22:37           ` [Intel-wired-lan] " Jesus Sanchez-Palencia
2017-10-18 22:37             ` Jesus Sanchez-Palencia
2017-10-19 20:39             ` [Intel-wired-lan] " Richard Cochran
2017-10-19 20:39               ` Richard Cochran
2017-10-23 17:18               ` [Intel-wired-lan] " Jesus Sanchez-Palencia
2017-10-23 17:18                 ` Jesus Sanchez-Palencia
2017-09-20  5:58         ` [Intel-wired-lan] " Richard Cochran
2017-09-20  5:58           ` Richard Cochran
2017-09-18  8:12 ` [Intel-wired-lan] " Richard Cochran
2017-09-18  8:12   ` Richard Cochran
2017-09-20  5:17   ` [Intel-wired-lan] TSN Scorecard, was " levipearson
2017-09-20  5:17     ` levipearson
2017-09-20  5:49     ` [Intel-wired-lan] " Richard Cochran
2017-09-20  5:49       ` Richard Cochran
2017-09-20 21:29       ` [Intel-wired-lan] " Jesus Sanchez-Palencia
2017-09-20 21:29         ` Jesus Sanchez-Palencia
2017-09-20  1:59 ` [Intel-wired-lan] " levipearson
2017-09-20  1:59   ` levipearson
2017-09-20  5:56   ` [Intel-wired-lan] " Richard Cochran
2017-09-20  5:56     ` Richard Cochran

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=1504821112.2117.8.camel@intel.com \
    --to=andre.guedes@intel.com \
    --cc=intel-wired-lan@osuosl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.