From: Jesse Brandeburg <jesse.brandeburg@linux.dev>
To: "Ertman, David M" <david.m.ertman@intel.com>,
"jbrandeb@kernel.org" <jbrandeb@kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Cc: "intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Nguyen, Anthony L" <anthony.l.nguyen@intel.com>,
"Kitszel, Przemyslaw" <przemyslaw.kitszel@intel.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net v1] ice: do not reserve resources for RDMA when disabled
Date: Fri, 15 Nov 2024 10:46:33 -0800 [thread overview]
Message-ID: <45ce4333-57da-4c32-ad06-c368d90b1328@linux.dev> (raw)
In-Reply-To: <IA1PR11MB619459AFADE5BB3A515C0577DD5B2@IA1PR11MB6194.namprd11.prod.outlook.com>
On 11/14/24 10:06 AM, Ertman, David M wrote:
>> case ICE_AQC_CAPS_RDMA:
>> - caps->rdma = (number == 1);
>> + if (IS_ENABLED(CONFIG_INFINIBAND_IRDMA))
>> + caps->rdma = (number == 1);
>> ice_debug(hw, ICE_DBG_INIT, "%s: rdma = %d\n", prefix,
>
> The HW caps struct should always accurately reflect the capabilities of the HW being probed. Since this
why must it accurately reflect the capability of the hardware? The
driver state and capability is a reflection of the combination of both,
so I'm not sure what the point of your statement.
> is a kernel configuration (i.e. software) consideration, the more appropriate approach would be to control
> the PF flag "ICE_FLAG_RDMA_ENA" based on the kernel CONFIG setting.
I started making the changes you suggested, but the ICE_FLAG_RDMA_ENA is
blindly set by the LAG code, if the cap.rdma is enabled. see
ice_set_rdma_cap(). This means the disable won't stick.
Unless I'm misunderstanding something, ICE_FLAG_RDMA_ENA is used both as
a gate and as a state, which is a design issue. This leaves no choice
but to implement the way I did in this v1 patch. Do you see any other
option to make a simple change that is safe for backporting to stable?
Thanks,
Jesse
next prev parent reply other threads:[~2024-11-15 18:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 0:00 [PATCH net v1] ice: do not reserve resources for RDMA when disabled jbrandeb
2024-11-14 11:32 ` Leon Romanovsky
2024-11-14 18:06 ` Ertman, David M
2024-11-15 18:46 ` Jesse Brandeburg [this message]
2024-11-22 1:50 ` Jesse Brandeburg
2024-11-22 22:35 ` Ertman, David M
2024-11-25 8:32 ` Przemek Kitszel
2024-11-15 8:51 ` Przemek Kitszel
2024-11-15 18:48 ` Jesse Brandeburg
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=45ce4333-57da-4c32-ad06-c368d90b1328@linux.dev \
--to=jesse.brandeburg@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=david.m.ertman@intel.com \
--cc=edumazet@google.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jbrandeb@kernel.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=przemyslaw.kitszel@intel.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).