Netdev Archive on
help / color / mirror / Atom feed
From: "Keller, Jacob E" <>
To: Jakub Kicinski <>,
	Kalesh A P <>
Cc: "" <>,
	"" <>,
	"" <>,
	"" <>,
	"" <>
Subject: Re: [PATCH net-next 0/2] devlink enhancements
Date: Mon, 2 Aug 2021 19:41:59 +0000	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On 8/2/2021 9:36 AM, Jakub Kicinski wrote:
> On Mon,  2 Aug 2021 09:57:38 +0530 Kalesh A P wrote:
>> From: Kalesh AP <>
>> This patchset adds device capability reporting to devlink info API.
>> It may be useful if we expose the device capabilities to the user
>> through devlink info API.
> Did you see the RFC Jake posted? That's way more palatable.

FWIW, my patch is more in regards to making sure that users, tools, or
scripts, have a way to tell if a given devlink interface is supported.

This seems like a way to indicate specific device features?

> Operationally the API provided here is of little to no value 
> to the user, and since it extends the "let the vendors dump custom
> meaningless strings" paradigm present in devlink please expect 
> major push back.

Right. the better approach here is to ensure that whatever user-facing
impact of these features is exposed through a standard interface. If one
doesn't exist for the capability, you will need to do work to create
such an interface.

If there's no user impact (and thus no need for a separate interface),
then why does a user need to know the capability?


      reply	other threads:[~2021-08-02 19:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-02  4:27 Kalesh A P
2021-08-02  4:27 ` [PATCH net-next 1/2] devlink: add device capability reporting to devlink info API Kalesh A P
2021-08-02  4:27 ` [PATCH net-next 2/2] bnxt_en: Add device capabilities to devlink info_get cb Kalesh A P
2021-08-02 16:36 ` [PATCH net-next 0/2] devlink enhancements Jakub Kicinski
2021-08-02 19:41   ` Keller, Jacob E [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \
    --subject='Re: [PATCH net-next 0/2] devlink enhancements' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).