From: Johannes Berg <johannes@sipsolutions.net>
To: "Adrián García Casado" <adriangarciacasado42@gmail.com>,
"Miri Korenblit" <miriam.rachel.korenblit@intel.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
Miguel Ojeda <miguel.ojeda.sandonis@gmail.com>
Subject: Re: [PATCH v3 1/3] wifi: iwlwifi: pcie: optimize MSI-X interrupt affinity
Date: Mon, 16 Mar 2026 11:32:43 +0100 [thread overview]
Message-ID: <c0dee26157e9e717864aca406dd10e928a13985e.camel@sipsolutions.net> (raw)
In-Reply-To: <20260315201647.15328-1-adriangarciacasado42@gmail.com>
Hi,
Somehow you messed up reposting this - the whole v2 series appears twice
and the v3 of this patch appears twice but without the rest of the
series?
> Implement a balanced RSS queue distribution by skipping CPU0 for
> high-rate MSI-X interrupts when multiple CPUs are online. This reduces
> contention with system housekeeping tasks on the boot core and improves
> overall throughput.
*Does* it improve throughput though? You should back up such claims with
numbers ... I doubt it would (unconditionally). It's not like the system
is going to be *really busy* all the time with housekeeping etc., and
the boot core is probably going to be a P-core, where you might have a
system with only 2 P-cores and 4-8 E (or even smaller) cores. This
likely also breaks some Intel-internal system requirements, but that
could be debated with the right folks.
Either way,
> --- a/drivers/net/wireless/intel/iwlwifi/pcie/gen1_2/trans.c
> +++ b/drivers/net/wireless/intel/iwlwifi/pcie/gen1_2/trans.c
> @@ -1683,7 +1683,17 @@ static void iwl_pcie_irq_set_affinity(struct iwl_trans *trans,
> * Get the cpu prior to the place to search
> * (i.e. return will be > i - 1).
> */
> + /*
> + * Balanced distribution: skip CPU0 for high-rate RSS queues
> + * to avoid contention with system housekeeping.
> + */
> cpu = cpumask_next(i - offset, cpu_online_mask);
> + if (cpu >= nr_cpu_ids)
> + cpu = cpumask_first(cpu_online_mask);
> +
> + if (cpu == 0 && num_online_cpus() > 1)
> + cpu = cpumask_next(0, cpu_online_mask);
> +
this is wrong since you really then should allocate one queue less,
rather than mapping two queues to the same core.
johannes
next prev parent reply other threads:[~2026-03-16 10:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-15 20:16 Adrián García Casado
2026-03-16 10:32 ` Johannes Berg [this message]
-- strict thread matches above, loose matches on Subject: below --
2026-03-15 20:10 Adrián García Casado
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=c0dee26157e9e717864aca406dd10e928a13985e.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=adriangarciacasado42@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miguel.ojeda.sandonis@gmail.com \
--cc=miriam.rachel.korenblit@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
all inboxes | Powered by JetHome®