Intel-Wired-Lan Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Tariq Toukan <ttoukan.linux@gmail.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [PATCH v3 14/14] net/mlx4: Use irq_update_affinity_hint
Date: Wed, 14 Jul 2021 14:19:20 +0300	[thread overview]
Message-ID: <c2d794bf-20b4-95fa-dfba-e85cf6b74bd4@gmail.com> (raw)
In-Reply-To: <20210713211502.464259-15-nitesh@redhat.com>



On 7/14/2021 12:15 AM, Nitesh Narayan Lal wrote:
> The driver uses irq_set_affinity_hint() to update the affinity_hint mask
> that is consumed by the userspace to distribute the interrupts. However,
> under the hood irq_set_affinity_hint() also applies the provided cpumask
> (if not NULL) as the affinity for the given interrupt which is an
> undocumented side effect.
> 
> To remove this side effect irq_set_affinity_hint() has been marked
> as deprecated and new interfaces have been introduced. Hence, replace the
> irq_set_affinity_hint() with the new interface irq_update_affinity_hint()
> that only updates the affinity_hint pointer.
> 
> Signed-off-by: Nitesh Narayan Lal <nitesh@redhat.com>
> Reviewed-by: Leon Romanovsky <leonro@nvidia.com>
> ---

Thanks for you patch.
Reviewed-by: Tariq Toukan <tariqt@nvidia.com>

Tariq

      reply	other threads:[~2021-07-14 11:19 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-13 21:14 [Intel-wired-lan] [PATCH v3 00/14] genirq: Cleanup the usage of irq_set_affinity_hint Nitesh Narayan Lal
2021-07-13 21:14 ` [Intel-wired-lan] [PATCH v3 01/14] genirq: Provide new interfaces for affinity hints Nitesh Narayan Lal
2021-07-13 21:14 ` [Intel-wired-lan] [PATCH v3 02/14] iavf: Use irq_update_affinity_hint Nitesh Narayan Lal
2021-07-13 21:51   ` Jesse Brandeburg
2021-07-13 21:14 ` [Intel-wired-lan] [PATCH v3 03/14] i40e: " Nitesh Narayan Lal
2021-07-13 21:52   ` Jesse Brandeburg
2021-07-13 21:14 ` [Intel-wired-lan] [PATCH v3 04/14] scsi: megaraid_sas: Use irq_set_affinity_and_hint Nitesh Narayan Lal
2021-07-13 21:14 ` [Intel-wired-lan] [PATCH v3 05/14] scsi: mpt3sas: " Nitesh Narayan Lal
2021-07-13 21:14 ` [Intel-wired-lan] [PATCH v3 06/14] RDMA/irdma: " Nitesh Narayan Lal
2021-07-14 12:03   ` Leon Romanovsky
2021-07-14 12:56     ` Nitesh Lal
2021-07-14 13:02       ` Leon Romanovsky
2021-07-15 13:25         ` Nitesh Lal
2021-07-13 21:14 ` [Intel-wired-lan] [PATCH v3 07/14] enic: Use irq_update_affinity_hint Nitesh Narayan Lal
2021-07-13 21:14 ` [Intel-wired-lan] [PATCH v3 08/14] be2net: " Nitesh Narayan Lal
2021-07-13 21:14 ` [Intel-wired-lan] [PATCH v3 09/14] ixgbe: " Nitesh Narayan Lal
2021-07-13 22:01   ` Jesse Brandeburg
2021-07-13 21:14 ` [Intel-wired-lan] [PATCH v3 10/14] mailbox: " Nitesh Narayan Lal
2021-07-13 21:14 ` [Intel-wired-lan] [PATCH v3 11/14] scsi: lpfc: Use irq_set_affinity Nitesh Narayan Lal
2021-07-13 21:15 ` [Intel-wired-lan] [PATCH v3 12/14] hinic: Use irq_set_affinity_and_hint Nitesh Narayan Lal
2021-07-13 21:15 ` [Intel-wired-lan] [PATCH v3 13/14] net/mlx5: " Nitesh Narayan Lal
2021-07-14 12:01   ` Leon Romanovsky
2021-07-13 21:15 ` [Intel-wired-lan] [PATCH v3 14/14] net/mlx4: Use irq_update_affinity_hint Nitesh Narayan Lal
2021-07-14 11:19   ` Tariq Toukan [this message]

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=c2d794bf-20b4-95fa-dfba-e85cf6b74bd4@gmail.com \
    --to=ttoukan.linux@gmail.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