public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>,
	Jiri Pirko <jiri@resnulli.us>
Cc: wojciech.drewek@intel.com, marcin.szycik@intel.com,
	netdev@vger.kernel.org, konrad.knitter@intel.com,
	pawel.chmielewski@intel.com, intel-wired-lan@lists.osuosl.org,
	pio.raczynski@gmail.com, sridhar.samudrala@intel.com,
	jacob.e.keller@intel.com, przemyslaw.kitszel@intel.com
Subject: Re: [Intel-wired-lan] [iwl-next v3 1/8] ice: devlink PF MSI-X max and min parameter
Date: Fri, 9 Aug 2024 07:30:16 +0200	[thread overview]
Message-ID: <3975b135-25ae-4576-ba61-db0f51fcf987@molgen.mpg.de> (raw)
In-Reply-To: <08fbb337-d2f1-47a7-871e-3890b34a782f@molgen.mpg.de>

[Cc: -nex.sw.ncis.nat.hpm.dev@intel.com (550 #5.1.0 Address rejected.)]

Am 09.08.24 um 07:18 schrieb Paul Menzel:
> Dear Michal,
> 
> 
> Thank you for your patch.
> 
> Am 09.08.24 um 07:13 schrieb Michal Swiatkowski:
>> On Thu, Aug 08, 2024 at 05:34:35PM +0200, Jiri Pirko wrote:
>>> Thu, Aug 08, 2024 at 09:20:09AM CEST, 
>>> michal.swiatkowski@linux.intel.com wrote:
>>>> Use generic devlink PF MSI-X parameter to allow user to change MSI-X
>>>> range.
>>>>
>>>> Reviewed-by: Wojciech Drewek <wojciech.drewek@intel.com>
>>>> Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
>>>> ---
>>>> .../net/ethernet/intel/ice/devlink/devlink.c  | 56 ++++++++++++++++++-
>>>> drivers/net/ethernet/intel/ice/ice.h          |  8 +++
>>>> drivers/net/ethernet/intel/ice/ice_irq.c      | 14 ++++-
>>>> 3 files changed, 76 insertions(+), 2 deletions(-)
>>>>
>>>> diff --git a/drivers/net/ethernet/intel/ice/devlink/devlink.c b/ 
>>>> drivers/net/ethernet/intel/ice/devlink/devlink.c
>>>> index 29a5f822cb8b..bdc22ea13e0f 100644
>>>> --- a/drivers/net/ethernet/intel/ice/devlink/devlink.c
>>>> +++ b/drivers/net/ethernet/intel/ice/devlink/devlink.c
>>>> @@ -1518,6 +1518,32 @@ static int 
>>>> ice_devlink_local_fwd_validate(struct devlink *devlink, u32 id,
>>>>     return 0;
>>>> }
>>>>
>>>> +static int
>>>> +ice_devlink_msix_max_pf_validate(struct devlink *devlink, u32 id,
>>>> +                 union devlink_param_value val,
>>>> +                 struct netlink_ext_ack *extack)
>>>> +{
>>>> +    if (val.vu16 > ICE_MAX_MSIX) {
>>>> +        NL_SET_ERR_MSG_MOD(extack, "PF max MSI-X is too high");
>>>
>>> No reason to have "PF" in the text. Also, no reason to have "max MSI-X".
>>> That is the name of the param.
>>
>> Ok, will change both, thanks.
> 
> Maybe also print both values in the error message?
> 
>>>> +        return -EINVAL;
>>>> +    }
>>>> +
>>>> +    return 0;
>>>> +}
> 
> […]
> 
> 
> Kind regards,
> 
> Paul

  reply	other threads:[~2024-08-09  5:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-08  7:20 [iwl-next v3 0/8] ice: managing MSI-X in driver Michal Swiatkowski
2024-08-08  7:20 ` [iwl-next v3 1/8] ice: devlink PF MSI-X max and min parameter Michal Swiatkowski
2024-08-08 15:34   ` Jiri Pirko
2024-08-09  5:13     ` Michal Swiatkowski
2024-08-09  5:18       ` [Intel-wired-lan] " Paul Menzel
2024-08-09  5:30         ` Paul Menzel [this message]
2024-08-09 10:52         ` Jiri Pirko
2024-08-09 10:51       ` Jiri Pirko
2024-08-09 11:05         ` Michal Swiatkowski
2024-08-09 11:29           ` Jiri Pirko
2024-08-09 11:39             ` Michal Swiatkowski
2024-08-10  6:33               ` Jiri Pirko
2024-08-08  7:20 ` [iwl-next v3 2/8] ice: remove splitting MSI-X between features Michal Swiatkowski
2024-08-08  7:20 ` [iwl-next v3 3/8] ice: get rid of num_lan_msix field Michal Swiatkowski
2024-08-08  7:20 ` [iwl-next v3 4/8] ice, irdma: move interrupts code to irdma Michal Swiatkowski
2024-08-08  7:20 ` [iwl-next v3 5/8] ice: treat dyn_allowed only as suggestion Michal Swiatkowski
2024-08-08  7:20 ` [iwl-next v3 6/8] ice: enable_rdma devlink param Michal Swiatkowski
2024-08-08  7:20 ` [iwl-next v3 7/8] ice: simplify VF MSI-X managing Michal Swiatkowski
2024-08-08  7:20 ` [iwl-next v3 8/8] ice: init flow director before RDMA Michal Swiatkowski

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=3975b135-25ae-4576-ba61-db0f51fcf987@molgen.mpg.de \
    --to=pmenzel@molgen.mpg.de \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jacob.e.keller@intel.com \
    --cc=jiri@resnulli.us \
    --cc=konrad.knitter@intel.com \
    --cc=marcin.szycik@intel.com \
    --cc=michal.swiatkowski@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pawel.chmielewski@intel.com \
    --cc=pio.raczynski@gmail.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=sridhar.samudrala@intel.com \
    --cc=wojciech.drewek@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