From: Abhijit Gangurde <abhijit.gangurde@amd.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: netdev@vger.kernel.org, linux-rdma@vger.kernel.org,
Brett Creeley <brett.creeley@amd.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Allen Hubbe <allen.hubbe@amd.com>, Jason Gunthorpe <jgg@ziepe.ca>,
Leon Romanovsky <leon@kernel.org>,
Eric Joyner <eric.joyner@amd.com>
Subject: Re: [PATCH net-next 0/4] RDMA/net/ionic: Misc updates
Date: Thu, 14 May 2026 20:03:09 +0530 [thread overview]
Message-ID: <4dc23648-7ec1-b68c-0e1b-282e014e534c@amd.com> (raw)
In-Reply-To: <20260506155954.17e984c6@kernel.org>
On 5/7/26 04:29, Jakub Kicinski wrote:
> On Tue, 5 May 2026 21:19:31 -0700 Eric Joyner wrote:
>> Other smaller additions add a devlink parameter to the ionic ethernet
>> driver for enabling and disabling RDMA,
> My understanding is that the devlink param was expected to change
> the configuration of the device. IOW user can enable/disable RDMA
> to save internal device resources. You seem to be purely preventing
> the auxbus device to be added. So there's nothing gained here compared
> to simply not loading the RDMA driver. What am I missing?
You're right that the current implementation controls only the auxiliary
bus device registration and doesn't reconfigure firmware resource
allocation. The intent behind this devlink param is to provide
per-device granularity for enabling/disabling RDMA. In a system with
multiple ionic NICs, an administrator may want RDMA active on some
devices but not others.
That said, if this per-device control justification is sufficient on its
own, or if firmware-side changes are a hard requirement for this to be
acceptable?
Thanks,
Abhijit
next prev parent reply other threads:[~2026-05-14 14:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-06 4:19 [PATCH net-next 0/4] RDMA/net/ionic: Misc updates Eric Joyner
2026-05-06 4:19 ` [PATCH net-next 1/4] RDMA/ionic: Update copyright year to 2026 Eric Joyner
2026-05-06 4:19 ` [PATCH net-next 2/4] net/ionic: Add devlink parameter for RDMA Eric Joyner
2026-05-06 4:19 ` [PATCH net-next 3/4] RDMA/ionic: Add debugfs support Eric Joyner
2026-05-13 7:21 ` Leon Romanovsky
2026-05-14 0:23 ` Jakub Kicinski
2026-05-14 6:00 ` Leon Romanovsky
2026-05-14 7:04 ` Greg Kroah-Hartman
2026-05-14 16:35 ` Leon Romanovsky
2026-05-06 4:19 ` [PATCH net-next 4/4] RDMA/ionic: Add DCQCN parameter configuration via debugfs Eric Joyner
2026-05-06 22:59 ` [PATCH net-next 0/4] RDMA/net/ionic: Misc updates Jakub Kicinski
2026-05-14 14:33 ` Abhijit Gangurde [this message]
2026-05-14 16:40 ` Leon Romanovsky
2026-05-14 17:19 ` Creeley, Brett
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=4dc23648-7ec1-b68c-0e1b-282e014e534c@amd.com \
--to=abhijit.gangurde@amd.com \
--cc=allen.hubbe@amd.com \
--cc=andrew+netdev@lunn.ch \
--cc=brett.creeley@amd.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=eric.joyner@amd.com \
--cc=jgg@ziepe.ca \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--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