From: Jakub Kicinski <kuba@kernel.org>
To: Parav Pandit <parav@nvidia.com>
Cc: David Wei <dw@davidwei.uk>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"edumazet@google.com" <edumazet@google.com>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"corbet@lwn.net" <corbet@lwn.net>,
"kalesh-anakkur.purayil@broadcom.com"
<kalesh-anakkur.purayil@broadcom.com>,
Saeed Mahameed <saeedm@nvidia.com>,
"leon@kernel.org" <leon@kernel.org>,
"jiri@resnulli.us" <jiri@resnulli.us>,
Shay Drori <shayd@nvidia.com>, Dan Jurgens <danielj@nvidia.com>,
Dima Chumak <dchumak@nvidia.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Jiri Pirko <jiri@nvidia.com>
Subject: Re: [net-next v3 1/2] devlink: Support setting max_io_eqs
Date: Thu, 4 Apr 2024 19:22:10 -0700 [thread overview]
Message-ID: <20240404192210.28e077bd@kernel.org> (raw)
In-Reply-To: <PH0PR12MB54811346FB97E174AD134F88DC3C2@PH0PR12MB5481.namprd12.prod.outlook.com>
On Thu, 4 Apr 2024 18:55:09 +0000 Parav Pandit wrote:
> > Yeah of course, thanks. I'm making some changes in netdevsim and can do a
> > drive-by cleanup there too.
> >
> Ok. yes, that will be helpful. Thanks.
I think that part is fine, TBH.
Drivers may not support particular control on particular HW/FW
for any number of reasons, we should let them return EOPNOTSUPP.
Not sure if there's much benefit for splitting the ops..
next prev parent reply other threads:[~2024-04-05 2:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 17:41 [net-next v3 0/2] devlink: Add port function attribute for IO EQs Parav Pandit
2024-04-03 17:41 ` [net-next v3 1/2] devlink: Support setting max_io_eqs Parav Pandit
2024-04-04 16:59 ` David Wei
2024-04-04 17:58 ` Parav Pandit
2024-04-04 18:40 ` David Wei
2024-04-04 18:50 ` Parav Pandit
2024-04-04 18:52 ` David Wei
2024-04-04 18:55 ` Parav Pandit
2024-04-05 2:22 ` Jakub Kicinski [this message]
2024-04-05 2:21 ` Jakub Kicinski
2024-04-05 3:13 ` Parav Pandit
2024-04-05 14:13 ` Jakub Kicinski
2024-04-05 16:34 ` Parav Pandit
2024-04-03 17:41 ` [net-next v3 2/2] mlx5/core: Support max_io_eqs for a function Parav Pandit
2024-04-04 3:51 ` Kalesh Anakkur Purayil
2024-04-04 16:57 ` David Wei
2024-04-04 18:05 ` Parav Pandit
2024-04-04 18:44 ` David Wei
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=20240404192210.28e077bd@kernel.org \
--to=kuba@kernel.org \
--cc=corbet@lwn.net \
--cc=danielj@nvidia.com \
--cc=davem@davemloft.net \
--cc=dchumak@nvidia.com \
--cc=dw@davidwei.uk \
--cc=edumazet@google.com \
--cc=jiri@nvidia.com \
--cc=jiri@resnulli.us \
--cc=kalesh-anakkur.purayil@broadcom.com \
--cc=leon@kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=shayd@nvidia.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).