Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jacob Keller <jacob.e.keller@intel.com>
To: <intel-wired-lan@osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH iwl-net 3/3] ice: map XDP queues to vectors in ice_vsi_map_rings_to_vectors()
Date: Thu, 16 May 2024 10:12:48 -0700	[thread overview]
Message-ID: <e607d810-cd39-493b-bd98-841d2c78b135@intel.com> (raw)
In-Reply-To: <20240516115942.GA443134@kernel.org>



On 5/16/2024 4:59 AM, Simon Horman wrote:
> On Thu, May 16, 2024 at 01:43:18PM +0200, Larysa Zaremba wrote:
>> On Thu, May 16, 2024 at 09:27:13AM +0100, Simon Horman wrote:
>>> On Wed, May 15, 2024 at 06:02:16PM +0200, Larysa Zaremba wrote:
>>>> ice_pf_dcb_recfg() re-maps queues to vectors with
>>>> ice_vsi_map_rings_to_vectors(), which does not restore the previous
>>>> state for XDP queues. This leads to no AF_XDP traffic after rebuild.
>>>>
>>>> Map XDP queues to vectors in ice_vsi_map_rings_to_vectors().
>>>> Also, move the code around, so XDP queues are mapped independently only
>>>> through .ndo_bpf().
>>>
>>> Hi Larysa,
>>>
>>> I take it the last sentence refers to the placement of ice_map_xdp_rings()
>>> in ice_prepare_xdp_rings() after rather than before the
>>> (cfg_type == ICE_XDP_CFG_PART) condition.
>>>
>>> If so, I see that it is a small change. But I do wonder if it is separate
>>> from fixing the issue described in the first paragraph. And thus would
>>> be better as a separate patch.
>>
>> This is not neccessary for the fix to work, but I think this is intergral to
>> making the change properly. I mean, before the change in the rebuild path we map
>> XDP rings to vectors only once and after the change we do this only once, just
>> previously it was in ice_prepare_xdp_rings() and now it is in
>> ice_vsi_map_rings_to_vectors().
>>
>>>
>>> Also, (I'm raising a separate issue :) breaking out logic into
>>> ice_xdp_ring_from_qid() seems very nice.  But I wonder if this ought to be
>>> part of a cleanup-patch for 'iwl' rather than a fixes patch for 'iwl-next'.
>>>
>>
>> I have separated this into a separate function, because 2 lines exceeded 80 
>> characters, which is not in line with our current style for drivers.
>> And I do not think that this small function creates any more additional 
>> potentian applying problems for this patch. And the change is small enough to 
>> see that the logic stays the same.
>>
>>> OTOH, I do see that breaking out ice_map_xdp_rings() makes sense in the
>>> context of this fix as the same logic is to be called in two places.
>>>
>>> Splitting patches aside, the resulting code looks good to me.
>>>
>>> ...
> 
> Hi Larysa,
> 
> Thanks for your explanation, this all seems reasonable to me.
> 
> Reviewed-by: Simon Horman <horms@kernel.org>
> 

Makes sense to me. With the context that it helps ensure we get the fix
right, we should send it together to net.

Thanks,
Jake

  reply	other threads:[~2024-05-16 17:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-05-15 16:02 [Intel-wired-lan] [PATCH iwl-net 0/3] Fix AF_XDP problems after changing queue number Larysa Zaremba
2024-05-15 16:02 ` [Intel-wired-lan] [PATCH iwl-net 1/3] ice: remove af_xdp_zc_qps bitmap Larysa Zaremba
2024-05-16  8:27   ` Simon Horman
2024-05-30  5:53   ` Rout, ChandanX
2024-05-15 16:02 ` [Intel-wired-lan] [PATCH iwl-net 2/3] ice: add flag to distinguish reset from .ndo_bpf in XDP rings config Larysa Zaremba
2024-05-16  8:27   ` Simon Horman
2024-05-16 10:00   ` Sergey Temerkhanov
2024-05-30  5:55   ` Rout, ChandanX
2024-05-15 16:02 ` [Intel-wired-lan] [PATCH iwl-net 3/3] ice: map XDP queues to vectors in ice_vsi_map_rings_to_vectors() Larysa Zaremba
2024-05-16  8:27   ` Simon Horman
2024-05-16 11:43     ` Larysa Zaremba
2024-05-16 11:59       ` Simon Horman
2024-05-16 17:12         ` Jacob Keller [this message]
2024-05-30  5:57   ` Rout, ChandanX

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=e607d810-cd39-493b-bd98-841d2c78b135@intel.com \
    --to=jacob.e.keller@intel.com \
    --cc=intel-wired-lan@osuosl.org \
    /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