From: Xiaoliang Yang <xiaoliang.yang_1@nxp.com>
To: Vladimir Oltean <olteanv@gmail.com>
Cc: "davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Arvid.Brodin@xdin.com" <Arvid.Brodin@xdin.com>,
"m-karicheri2@ti.com" <m-karicheri2@ti.com>,
"vinicius.gomes@intel.com" <vinicius.gomes@intel.com>,
"michael.chan@broadcom.com" <michael.chan@broadcom.com>,
"vishal@chelsio.com" <vishal@chelsio.com>,
"saeedm@mellanox.com" <saeedm@mellanox.com>,
"jiri@mellanox.com" <jiri@mellanox.com>,
"idosch@mellanox.com" <idosch@mellanox.com>,
"alexandre.belloni@bootlin.com" <alexandre.belloni@bootlin.com>,
"UNGLinuxDriver@microchip.com" <UNGLinuxDriver@microchip.com>,
"ivan.khoronzhuk@linaro.org" <ivan.khoronzhuk@linaro.org>,
"andre.guedes@linux.intel.com" <andre.guedes@linux.intel.com>,
"yuehaibing@huawei.com" <yuehaibing@huawei.com>,
"allan.nielsen@microchip.com" <allan.nielsen@microchip.com>,
"joergen.andreasen@microchip.com"
<joergen.andreasen@microchip.com>,
"colin.king@canonical.com" <colin.king@canonical.com>,
Po Liu <po.liu@nxp.com>, Mingkai Hu <mingkai.hu@nxp.com>,
Claudiu Manoil <claudiu.manoil@nxp.com>,
Vladimir Oltean <vladimir.oltean@nxp.com>,
Leo Li <leoyang.li@nxp.com>
Subject: RE: [EXT] Re: [net-next] net: dsa: felix: disable always guard band bit for TAS config
Date: Tue, 20 Apr 2021 03:06:40 +0000 [thread overview]
Message-ID: <DB8PR04MB5785E8D0499961D6C046092AF0489@DB8PR04MB5785.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <20210419123825.oicleie44ms6zcve@skbuf>
Hi Vladimir.
On Mon, Apr 19, 2021 at 20:38PM +0800, Vladimir Oltean wrote:
>
>What is a scheduled queue? When time-aware scheduling is enabled on the port, why are some queues scheduled and some not?
The felix vsc9959 device can set SCH_TRAFFIC_QUEUES field bits to define which queue is scheduled. Only the set queues serves schedule traffic. In this driver we set all 8 queues to be scheduled in default, so all the traffic are schedule queues to
schedule queue.
Thanks,
Xiaoliang Yang
next prev parent reply other threads:[~2021-04-20 3:06 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 10:25 [net-next] net: dsa: felix: disable always guard band bit for TAS config Xiaoliang Yang
2021-04-19 12:38 ` Vladimir Oltean
2021-04-20 3:06 ` Xiaoliang Yang [this message]
2021-04-20 8:26 ` [EXT] " Vladimir Oltean
2021-04-20 10:28 ` Xiaoliang Yang
2021-04-20 10:30 ` Vladimir Oltean
2021-04-20 10:42 ` Vladimir Oltean
2021-04-21 2:51 ` Xiaoliang Yang
2021-04-20 10:33 ` Vladimir Oltean
2021-04-20 23:20 ` patchwork-bot+netdevbpf
2021-05-04 17:05 ` Michael Walle
2021-05-04 18:18 ` Vladimir Oltean
2021-05-04 18:38 ` Michael Walle
2021-05-04 18:50 ` Vladimir Oltean
2021-05-04 19:08 ` Michael Walle
2021-05-04 19:17 ` Vladimir Oltean
2021-05-04 20:23 ` Michael Walle
2021-05-04 21:33 ` Vladimir Oltean
2021-05-06 13:25 ` Michael Walle
2021-05-06 13:50 ` Vladimir Oltean
2021-05-06 14:20 ` Michael Walle
2021-05-06 14:41 ` Michael Walle
2021-05-06 15:07 ` Vladimir Oltean
2021-05-06 18:28 ` Michael Walle
2021-05-07 7:16 ` [EXT] " Xiaoliang Yang
2021-05-07 7:35 ` Michael Walle
2021-05-07 11:09 ` Xiaoliang Yang
2021-05-07 12:19 ` Vladimir Oltean
2021-05-07 12:43 ` Michael Walle
2021-06-07 11:26 ` Michael Walle
2021-06-09 8:06 ` [EXT] " Xiaoliang Yang
2021-06-09 8:41 ` Michael Walle
2021-05-07 12:19 ` Michael Walle
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=DB8PR04MB5785E8D0499961D6C046092AF0489@DB8PR04MB5785.eurprd04.prod.outlook.com \
--to=xiaoliang.yang_1@nxp.com \
--cc=Arvid.Brodin@xdin.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=allan.nielsen@microchip.com \
--cc=andre.guedes@linux.intel.com \
--cc=claudiu.manoil@nxp.com \
--cc=colin.king@canonical.com \
--cc=davem@davemloft.net \
--cc=idosch@mellanox.com \
--cc=ivan.khoronzhuk@linaro.org \
--cc=jiri@mellanox.com \
--cc=joergen.andreasen@microchip.com \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m-karicheri2@ti.com \
--cc=michael.chan@broadcom.com \
--cc=mingkai.hu@nxp.com \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=po.liu@nxp.com \
--cc=saeedm@mellanox.com \
--cc=vinicius.gomes@intel.com \
--cc=vishal@chelsio.com \
--cc=vladimir.oltean@nxp.com \
--cc=yuehaibing@huawei.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).