From: Jakub Kicinski <kuba@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: "David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew@lunn.ch>, Eric Dumazet <edumazet@google.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Paolo Abeni <pabeni@redhat.com>,
Vladimir Oltean <olteanv@gmail.com>,
Woojung Huh <woojung.huh@microchip.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net-next v2 0/2] net: dsa: microchip: tc-ets support
Date: Mon, 13 Mar 2023 12:18:33 -0700 [thread overview]
Message-ID: <20230313121833.1942244e@kernel.org> (raw)
In-Reply-To: <20230310090809.220764-1-o.rempel@pengutronix.de>
On Fri, 10 Mar 2023 10:08:07 +0100 Oleksij Rempel wrote:
> changes v3:
> - add tc_ets_supported to match supported devices
> - dynamically regenerated default TC to queue map.
> - add Acked-by to the first patch
>
> changes v2:
> - run egress limit configuration on all queue separately. Otherwise
> configuration may not apply correctly.
I thought Vladimir was suggesting mqprio, could you summarize the take
aways from that discussion?
next prev parent reply other threads:[~2023-03-13 19:20 UTC|newest]
Thread overview: 11+ 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
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 [this message]
2023-03-14 8:01 ` Oleksij Rempel
2023-03-15 8:10 ` patchwork-bot+netdevbpf
-- strict thread matches above, loose matches on Subject: below --
2023-03-08 9:12 Oleksij Rempel
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=20230313121833.1942244e@kernel.org \
--to=kuba@kernel.org \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=woojung.huh@microchip.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 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.