public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Woojung.Huh@microchip.com
Cc: davem@davemloft.net, andrew@lunn.ch, edumazet@google.com,
	f.fainelli@gmail.com, kuba@kernel.org, pabeni@redhat.com,
	olteanv@gmail.com, Arun.Ramadoss@microchip.com,
	kernel@pengutronix.de, linux-kernel@vger.kernel.org,
	netdev@vger.kernel.org, UNGLinuxDriver@microchip.com,
	dsahern@kernel.org, horms@kernel.org, willemb@google.com,
	san@skov.dk
Subject: Re: [PATCH net-next v7 02/12] net: dsa: microchip: add IPV information support
Date: Tue, 7 May 2024 06:37:36 +0200	[thread overview]
Message-ID: <ZjmwEPS0BM0QJUc5@pengutronix.de> (raw)
In-Reply-To: <BL0PR11MB29131C40E4B39B119F9891C2E71C2@BL0PR11MB2913.namprd11.prod.outlook.com>

Hi Woojung,

On Mon, May 06, 2024 at 08:43:48PM +0000, Woojung.Huh@microchip.com wrote:
> Hi Oleksij,
> 
> Thanks for the patch and sorry about late comment on this.
> 
> I have a comment on the name of IPV (Internal Priority Value)
> IPV is added and used term in 802.1Qci PSFP
> (https://ieeexplore.ieee.org/document/8064221) and, merged into 802.1Q (from 802.1Q-2018)
> for another functions. 
> 
> Even it does similar operation holding temporal priority value internally (as it is named),
> because KSZ datasheet doesn't use the term of IPV (Internal Priority Value) and
> avoiding any confusion later when PSFP is in the Linux world,
> I would like to recommend a different name such as IPM (Internal Priority Mapping) than IPV.
> 
> How do you think?

Ok.

Do IPV in LAN9372 datasheet means, IPV 802.1Qci PSFP or IPM?

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

  reply	other threads:[~2024-05-07  4:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-03 13:13 [PATCH net-next v7 00/12] add DCB and DSCP support for KSZ switches Oleksij Rempel
2024-05-03 13:13 ` [PATCH net-next v7 01/12] net: dsa: add support for DCB get/set apptrust configuration Oleksij Rempel
2024-05-03 13:13 ` [PATCH net-next v7 02/12] net: dsa: microchip: add IPV information support Oleksij Rempel
2024-05-06 20:43   ` Woojung.Huh
2024-05-07  4:37     ` Oleksij Rempel [this message]
2024-05-07 15:04       ` Woojung.Huh
2024-05-03 13:13 ` [PATCH net-next v7 03/12] net: add IEEE 802.1q specific helpers Oleksij Rempel
2024-05-03 13:13 ` [PATCH net-next v7 04/12] net: dsa: microchip: add multi queue support for KSZ88X3 variants Oleksij Rempel
2024-05-03 13:13 ` [PATCH net-next v7 05/12] net: dsa: microchip: add support for different DCB app configurations Oleksij Rempel
2024-05-03 13:13 ` [PATCH net-next v7 06/12] net: dsa: microchip: dcb: add special handling for KSZ88X3 family Oleksij Rempel
2024-05-03 13:13 ` [PATCH net-next v7 07/12] net: dsa: microchip: enable ETS support for KSZ989X variants Oleksij Rempel
2024-05-03 13:13 ` [PATCH net-next v7 08/12] net: dsa: microchip: init predictable IPV to queue mapping for all non KSZ8xxx variants Oleksij Rempel
2024-05-06 14:40   ` Arun.Ramadoss
2024-05-03 13:13 ` [PATCH net-next v7 09/12] net: dsa: microchip: let DCB code do PCP and DSCP policy configuration Oleksij Rempel
2024-05-03 13:13 ` [PATCH net-next v7 10/12] net: dsa: add support switches global DSCP priority mapping Oleksij Rempel
2024-05-03 13:13 ` [PATCH net-next v7 11/12] net: dsa: microchip: add support " Oleksij Rempel
2024-05-03 13:13 ` [PATCH net-next v7 12/12] selftests: microchip: add test for QoS support on KSZ9477 switch family Oleksij Rempel
2024-05-08  9:40 ` [PATCH net-next v7 00/12] add DCB and DSCP support for KSZ switches 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=ZjmwEPS0BM0QJUc5@pengutronix.de \
    --to=o.rempel@pengutronix.de \
    --cc=Arun.Ramadoss@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=horms@kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=san@skov.dk \
    --cc=willemb@google.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