From: Vladimir Oltean <olteanv@gmail.com>
To: Xiaoliang Yang <xiaoliang.yang_1@nxp.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Arvid.Brodin@xdin.com,
m-karicheri2@ti.com, vinicius.gomes@intel.com,
michael.chan@broadcom.com, vishal@chelsio.com,
saeedm@mellanox.com, jiri@mellanox.com, idosch@mellanox.com,
alexandre.belloni@bootlin.com, UNGLinuxDriver@microchip.com,
ivan.khoronzhuk@linaro.org, andre.guedes@linux.intel.com,
yuehaibing@huawei.com, allan.nielsen@microchip.com,
joergen.andreasen@microchip.com, colin.king@canonical.com,
po.liu@nxp.com, mingkai.hu@nxp.com, claudiu.manoil@nxp.com,
vladimir.oltean@nxp.com, leoyang.li@nxp.com
Subject: Re: [net-next] net: dsa: felix: disable always guard band bit for TAS config
Date: Mon, 19 Apr 2021 15:38:25 +0300 [thread overview]
Message-ID: <20210419123825.oicleie44ms6zcve@skbuf> (raw)
In-Reply-To: <20210419102530.20361-1-xiaoliang.yang_1@nxp.com>
Hi Xiaoliang,
On Mon, Apr 19, 2021 at 06:25:30PM +0800, Xiaoliang Yang wrote:
> ALWAYS_GUARD_BAND_SCH_Q bit in TAS config register is descripted as
> this:
> 0: Guard band is implemented for nonschedule queues to schedule
> queues transition.
> 1: Guard band is implemented for any queue to schedule queue
> transition.
>
> The driver set guard band be implemented for any queue to schedule queue
> transition before, which will make each GCL time slot reserve a guard
> band time that can pass the max SDU frame. Because guard band time could
> not be set in tc-taprio now, it will use about 12000ns to pass 1500B max
> SDU. This limits each GCL time interval to be more than 12000ns.
>
> This patch change the guard band to be only implemented for nonschedule
> queues to schedule queues transition, so that there is no need to reserve
> guard band on each GCL. Users can manually add guard band time for each
> schedule queues in their configuration if they want.
>
> Signed-off-by: Xiaoliang Yang <xiaoliang.yang_1@nxp.com>
> ---
What is a scheduled queue? When time-aware scheduling is enabled on the
port, why are some queues scheduled and some not?
next prev parent reply other threads:[~2021-04-19 12:38 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 [this message]
2021-04-20 3:06 ` [EXT] " Xiaoliang Yang
2021-04-20 8:26 ` 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=20210419123825.oicleie44ms6zcve@skbuf \
--to=olteanv@gmail.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=po.liu@nxp.com \
--cc=saeedm@mellanox.com \
--cc=vinicius.gomes@intel.com \
--cc=vishal@chelsio.com \
--cc=vladimir.oltean@nxp.com \
--cc=xiaoliang.yang_1@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).