public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: <Arun.Ramadoss@microchip.com>
To: <o.rempel@pengutronix.de>
Cc: <olteanv@gmail.com>, <andrew@lunn.ch>,
	<linux-kernel@vger.kernel.org>, <UNGLinuxDriver@microchip.com>,
	<f.fainelli@gmail.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
	<edumazet@google.com>, <netdev@vger.kernel.org>,
	<Woojung.Huh@microchip.com>, <davem@davemloft.net>,
	<kernel@pengutronix.de>
Subject: Re: [PATCH net-next v3 2/2] net: dsa: microchip: add ETS Qdisc support for KSZ9477 series
Date: Mon, 13 Mar 2023 06:46:50 +0000	[thread overview]
Message-ID: <42e1c1fe287d7109e0a9c2d2d3f83fde6181d04e.camel@microchip.com> (raw)
In-Reply-To: <20230313053607.GD29822@pengutronix.de>

On Mon, 2023-03-13 at 06:36 +0100, Oleksij Rempel wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
> 
> On Mon, Mar 13, 2023 at 03:34:16AM +0000, Arun.Ramadoss@microchip.com
>  wrote:
> > Hi Oleksij,
> > On Fri, 2023-03-10 at 10:08 +0100, Oleksij Rempel wrote:
> > > EXTERNAL EMAIL: Do not click links or open attachments unless you
> > > know the content is safe
> > > 
> > > Add ETS Qdisc support for KSZ9477 of switches. Current
> > > implementation
> > > is
> > > limited to strict priority mode.
> > > 
> > > Tested on KSZ8563R with following configuration:
> > > tc qdisc replace dev lan2 root handle 1: ets strict 4 \
> > >   priomap 3 3 2 2 1 1 0 0
> > > ip link add link lan2 name v1 type vlan id 1 \
> > >   egress-qos-map 0:0 1:1 2:2 3:3 4:4 5:5 6:6 7:7
> > > 
> > > and patched iperf3 version:
> > > https://github.com/esnet/iperf/pull/1476
> > > iperf3 -c 172.17.0.1 -b100M  -l1472 -t100 -u -R --sock-prio 2
> > > 
> > > Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> > > ---
> > >  drivers/net/dsa/microchip/ksz_common.c | 218
> > > +++++++++++++++++++++++++
> > >  drivers/net/dsa/microchip/ksz_common.h |  12 ++
> > >  2 files changed, 230 insertions(+)
> > > 
> > > diff --git a/drivers/net/dsa/microchip/ksz_common.c
> > > b/drivers/net/dsa/microchip/ksz_common.c
> > > index ae05fe0b0a81..54d75ec22ef0 100644
> > > --- a/drivers/net/dsa/microchip/ksz_common.c
> > > +++ b/drivers/net/dsa/microchip/ksz_common.c
> > > @@ -1087,6 +1087,7 @@ const struct ksz_chip_data
> > > ksz_switch_chips[] =
> > > {
> > >                 .port_nirqs = 3,
> > >                 .num_tx_queues = 4,
> > >                 .tc_cbs_supported = true,
> > > +               .tc_ets_supported = true,
> > 
> > Whether the switch which are supporting cbs will also support ets
> > or
> > not. If CBS and ETS are related, then is it possible to use single
> > flag
> > controlling both the feature. I could infer that switch which has
> > tc_cbs_supported  true, also has tc_ets_supported also true.
> > 
> > If both are different, patch looks good to me.
> 
> Both are different. For example on ksz8 switches it is possible to
> implement tc-etc but not tc-cbs.

Ok. 

Acked-by: Arun Ramadoss <arun.ramadoss@microchip.com>

> 
> Regatds,
> Oleksij
> --
> Pengutronix
> e.K.                           |                             |
> Steuerwalder Str. 21                       | 
> http://www.pengutronix.de/e/  |
> 31137 Hildesheim, Germany                  | Phone: +49-5121-206917-
> 0    |
> Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-
> 5555 |

  reply	other threads:[~2023-03-13  6:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-10  9:08 [PATCH net-next v2 0/2] net: dsa: microchip: tc-ets support Oleksij Rempel
2023-03-10  9:08 ` [PATCH net-next v3 1/2] net: dsa: microchip: add ksz_setup_tc_mode() function Oleksij Rempel
2023-03-10  9:08 ` [PATCH net-next v3 2/2] net: dsa: microchip: add ETS Qdisc support for KSZ9477 series Oleksij Rempel
2023-03-13  3:34   ` Arun.Ramadoss
2023-03-13  5:36     ` Oleksij Rempel
2023-03-13  6:46       ` Arun.Ramadoss [this message]
2023-03-13  6:48 ` [PATCH net-next v2 0/2] net: dsa: microchip: tc-ets support Arun.Ramadoss
2023-03-13 19:18 ` Jakub Kicinski
2023-03-14  8:01   ` Oleksij Rempel
2023-03-15  8:10 ` patchwork-bot+netdevbpf

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=42e1c1fe287d7109e0a9c2d2d3f83fde6181d04e.camel@microchip.com \
    --to=arun.ramadoss@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.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