From: Ahmed Zaki <ahmed.zaki@intel.com>
To: Simon Horman <horms@kernel.org>
Cc: <intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>,
"Madhu Chittim" <madhu.chittim@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH iwl-next] idpf: preserve coalescing settings across resets
Date: Mon, 23 Jun 2025 09:48:02 -0600 [thread overview]
Message-ID: <c4164071-60c8-4b06-a710-70d5fbef2b11@intel.com> (raw)
In-Reply-To: <20250621121346.GD71935@horms.kernel.org>
On 2025-06-21 6:13 a.m., Simon Horman wrote:
> On Fri, Jun 20, 2025 at 11:15:48AM -0600, Ahmed Zaki wrote:
>> The IRQ coalescing config currently reside only inside struct
>> idpf_q_vector. However, all idpf_q_vector structs are de-allocated and
>> re-allocated during resets. This leads to user-set coalesce configuration
>> to be lost.
>>
>> Add new fields to struct idpf_vport_user_config_data to save the user
>> settings and re-apply them after reset.
>>
>> Reviewed-by: Madhu Chittim <madhu.chittim@intel.com>
>> Signed-off-by: Ahmed Zaki <ahmed.zaki@intel.com>
>
> Hi Ahmed,
>
> I am wondering if this patch also preserves coalescing settings in the case
> where.
>
> 1. User sets coalescence for n queues
> 2. The number of queues is reduced, say to m (where m < n)
> 3. The user then increases the number of queues, say back to n
>
> It seems to me that in this scenario it's reasonable to preserve
> the settings for queues 0 to m, bit not queues m + 1 to n.
Hi Simon,
I just did a quick test and it seems new settings are preserved in the
above scenario: all n queues have the new coalescing settings.
>
> But perhaps this point is orthogonal to this change.
> I am unsure.
>
Agreed, but let me know if it is a showstopper.
Ahmed
next prev parent reply other threads:[~2025-06-23 15:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-20 17:15 [Intel-wired-lan] [PATCH iwl-next] idpf: preserve coalescing settings across resets Ahmed Zaki
2025-06-21 12:13 ` Simon Horman
2025-06-23 15:48 ` Ahmed Zaki [this message]
2025-06-24 9:40 ` Simon Horman
2025-06-24 16:13 ` Ahmed Zaki
2025-06-24 18:24 ` Simon Horman
2025-06-26 17:06 ` Willem de Bruijn
2025-07-07 22:16 ` Salin, Samuel
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=c4164071-60c8-4b06-a710-70d5fbef2b11@intel.com \
--to=ahmed.zaki@intel.com \
--cc=horms@kernel.org \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=madhu.chittim@intel.com \
--cc=netdev@vger.kernel.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