From: Ilias Apalodimas <ilias.apalodimas@linaro.org>
To: Vinicius Costa Gomes <vinicius.gomes@intel.com>
Cc: PO LIU <po.liu@nxp.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"haustad@cisco.com" <haustad@cisco.com>,
"nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
Mingkai Hu <mingkai.hu@nxp.com>, Roy Zang <roy.zang@nxp.com>
Subject: Re: [PATCH] net: tsn: add an netlink interface between kernel and application layer
Date: Thu, 3 Jan 2019 11:16:05 +0200 [thread overview]
Message-ID: <20190103091605.GA4597@apalos> (raw)
In-Reply-To: <87k1jm51ey.fsf@intel.com>
Hi Po,
> > Hi Vinicius,
> >
> > Thank you very much for your feedback.
> >
> > I know the CBS is used to be most important part of AVB. And qdiscs is good tool to configure qos.
> >
> > But as you know, the TSN family is a cluster of protocols and much extending the AVB. The protocols have different functionalities and they may have more than hundred parameters. For example NXP ls1028a support Qbv/Qci/Qbu/Qav and also the 8021CB (not included in this patch yet).
> >
> > Some protocols target to configure the traffic class(like Qav CBS).
> > Some to config the port(like Qbv). But some for the whole ethernet
> > controller(like Qci, the control entries for the whole controller,
> > which input ports and which output ports).
>
> Reading your email, now I understand your point a little better. You are
> interested in multi-port devices. I admit that I am not too familiar
> with how multi-port devices are exposed in Linux, I was only focused on
> the end-station use cases, until now.
Have you considered a switchdev-based driver for multi-port devices?
What you ask of TSN configuration is currently doable with switch switchdev for
VLANs and other similar networking functionality.
Instead of rewriting this from scratch, we not extend the currect TC and
switchdev functionality for that ?
Regards
/Ilias
next prev parent reply other threads:[~2019-01-03 9:16 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1545968772-7237-1-git-send-email-Po.Liu@nxp.com>
2018-12-28 3:49 ` [PATCH] net: tsn: add an netlink interface between kernel and application layer PO LIU
2018-12-28 19:29 ` Vinicius Costa Gomes
2018-12-29 1:59 ` PO LIU
2019-01-02 19:01 ` Vinicius Costa Gomes
2019-01-03 3:10 ` Po Liu
2019-01-03 9:16 ` Ilias Apalodimas [this message]
2019-01-03 10:09 ` Po Liu
2019-01-03 11:38 ` Ilias Apalodimas
2019-01-04 9:01 ` Po Liu
2019-01-04 9:19 ` Ilias Apalodimas
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=20190103091605.GA4597@apalos \
--to=ilias.apalodimas@linaro.org \
--cc=davem@davemloft.net \
--cc=gregkh@linuxfoundation.org \
--cc=haustad@cisco.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingkai.hu@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=po.liu@nxp.com \
--cc=roy.zang@nxp.com \
--cc=vinicius.gomes@intel.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).