From: Jakub Kicinski <kuba@kernel.org>
To: Nitesh Narayan Lal <nitesh@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-scsi@vger.kernel.org,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-api@vger.kernel.org, linux-pci@vger.kernel.org,
tglx@linutronix.de, jesse.brandeburg@intel.com,
robin.murphy@arm.com, mtosatti@redhat.com, mingo@kernel.org,
jbrandeb@kernel.org, frederic@kernel.org, juri.lelli@redhat.com,
abelits@marvell.com, bhelgaas@google.com, rostedt@goodmis.org,
peterz@infradead.org, davem@davemloft.net,
akpm@linux-foundation.org, sfr@canb.auug.org.au,
stephen@networkplumber.org, rppt@linux.vnet.ibm.com,
chris.friesen@windriver.com, maz@kernel.org,
nhorman@tuxdriver.com, pjwaskiewicz@gmail.com,
sassmann@redhat.com, thenzl@redhat.com,
kashyap.desai@broadcom.com, sumit.saxena@broadcom.com,
shivasharan.srikanteshwara@broadcom.com,
sathya.prakash@broadcom.com, sreekanth.reddy@broadcom.com,
suganath-prabu.subramani@broadcom.com, james.smart@broadcom.com,
dick.kennedy@broadcom.com, jkc@redhat.com,
faisal.latif@intel.com, shiraz.saleem@intel.com,
tariqt@nvidia.com, ahleihel@redhat.com, kheib@redhat.com,
borisp@nvidia.com, saeedm@nvidia.com, benve@cisco.com,
govind@gmx.com, jassisinghbrar@gmail.com,
ajit.khaparde@broadcom.com, sriharsha.basavapatna@broadcom.com,
somnath.kotur@broadcom.com, nilal@redhat.com,
tatyana.e.nikolova@intel.com, mustafa.ismail@intel.com,
ahs3@redhat.com, leonro@nvidia.com,
chandrakanth.patil@broadcom.com, bjorn.andersson@linaro.org,
chunkuang.hu@kernel.org, yongqiang.niu@mediatek.com,
baolin.wang7@gmail.com, poros@redhat.com, minlei@redhat.com,
emilne@redhat.com, jejb@linux.ibm.com,
martin.petersen@oracle.com, _govind@gmx.com,
ley.foon.tan@intel.com, kabel@kernel.org,
viresh.kumar@linaro.org, Tushar.Khandelwal@arm.com,
luobin9@huawei.com
Subject: Re: [PATCH v4 01/14] genirq: Provide new interfaces for affinity hints
Date: Tue, 20 Jul 2021 12:57:02 +0200 [thread overview]
Message-ID: <20210720125702.28053dd6@cakuba> (raw)
In-Reply-To: <20210719180746.1008665-2-nitesh@redhat.com>
On Mon, 19 Jul 2021 14:07:33 -0400, Nitesh Narayan Lal wrote:
> From: Thomas Gleixner <tglx@linutronix.de>
>
> The discussion about removing the side effect of irq_set_affinity_hint() of
> actually applying the cpumask (if not NULL) as affinity to the interrupt,
> unearthed a few unpleasantries:
>
> 1) The modular perf drivers rely on the current behaviour for the very
> wrong reasons.
>
> 2) While none of the other drivers prevents user space from changing
> the affinity, a cursorily inspection shows that there are at least
> expectations in some drivers.
>
> #1 needs to be cleaned up anyway, so that's not a problem
>
> #2 might result in subtle regressions especially when irqbalanced (which
> nowadays ignores the affinity hint) is disabled.
>
> Provide new interfaces:
>
> irq_update_affinity_hint() - Only sets the affinity hint pointer
> irq_set_affinity_and_hint() - Set the pointer and apply the affinity to
> the interrupt
>
> Make irq_set_affinity_hint() a wrapper around irq_apply_affinity_hint() and
> document it to be phased out.
>
> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
> Signed-off-by: Nitesh Narayan Lal <nitesh@redhat.com>
> Link: https://lore.kernel.org/r/20210501021832.743094-1-jesse.brandeburg@intel.com
include/linux/interrupt.h:343: warning: Function parameter or member 'm' not described in 'irq_update_affinity_hint'
include/linux/interrupt.h:343: warning: Excess function parameter 'cpumask' description in 'irq_update_affinity_hint'
include/linux/interrupt.h:358: warning: Function parameter or member 'm' not described in 'irq_set_affinity_and_hint'
include/linux/interrupt.h:358: warning: Excess function parameter 'cpumask' description in 'irq_set_affinity_and_hint'
next prev parent reply other threads:[~2021-07-20 11:01 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-19 18:07 [PATCH v4 00/14] genirq: Cleanup the usage of irq_set_affinity_hint Nitesh Narayan Lal
2021-07-19 18:07 ` [PATCH v4 01/14] genirq: Provide new interfaces for affinity hints Nitesh Narayan Lal
2021-07-20 10:57 ` Jakub Kicinski [this message]
2021-07-19 18:07 ` [PATCH v4 02/14] iavf: Use irq_update_affinity_hint Nitesh Narayan Lal
2021-07-19 18:07 ` [PATCH v4 03/14] i40e: " Nitesh Narayan Lal
2021-07-19 18:07 ` [PATCH v4 04/14] scsi: megaraid_sas: Use irq_set_affinity_and_hint Nitesh Narayan Lal
2021-07-19 18:07 ` [PATCH v4 05/14] scsi: mpt3sas: " Nitesh Narayan Lal
2021-07-19 18:07 ` [PATCH v4 06/14] RDMA/irdma: Use irq_update_affinity_hint Nitesh Narayan Lal
2021-07-19 18:07 ` [PATCH v4 07/14] enic: " Nitesh Narayan Lal
2021-07-19 18:07 ` [PATCH v4 08/14] be2net: " Nitesh Narayan Lal
2021-07-19 18:07 ` [PATCH v4 09/14] ixgbe: " Nitesh Narayan Lal
2021-07-19 18:07 ` [PATCH v4 10/14] mailbox: " Nitesh Narayan Lal
2021-07-19 18:07 ` [PATCH v4 11/14] scsi: lpfc: Use irq_set_affinity Nitesh Narayan Lal
2021-07-19 18:07 ` [PATCH v4 12/14] hinic: Use irq_set_affinity_and_hint Nitesh Narayan Lal
2021-07-19 18:07 ` [PATCH v4 13/14] net/mlx5: " Nitesh Narayan Lal
2021-07-19 18:07 ` [PATCH v4 14/14] net/mlx4: Use irq_update_affinity_hint Nitesh Narayan Lal
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=20210720125702.28053dd6@cakuba \
--to=kuba@kernel.org \
--cc=Tushar.Khandelwal@arm.com \
--cc=_govind@gmx.com \
--cc=abelits@marvell.com \
--cc=ahleihel@redhat.com \
--cc=ahs3@redhat.com \
--cc=ajit.khaparde@broadcom.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang7@gmail.com \
--cc=benve@cisco.com \
--cc=bhelgaas@google.com \
--cc=bjorn.andersson@linaro.org \
--cc=borisp@nvidia.com \
--cc=chandrakanth.patil@broadcom.com \
--cc=chris.friesen@windriver.com \
--cc=chunkuang.hu@kernel.org \
--cc=davem@davemloft.net \
--cc=dick.kennedy@broadcom.com \
--cc=emilne@redhat.com \
--cc=faisal.latif@intel.com \
--cc=frederic@kernel.org \
--cc=govind@gmx.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=james.smart@broadcom.com \
--cc=jassisinghbrar@gmail.com \
--cc=jbrandeb@kernel.org \
--cc=jejb@linux.ibm.com \
--cc=jesse.brandeburg@intel.com \
--cc=jkc@redhat.com \
--cc=juri.lelli@redhat.com \
--cc=kabel@kernel.org \
--cc=kashyap.desai@broadcom.com \
--cc=kheib@redhat.com \
--cc=leonro@nvidia.com \
--cc=ley.foon.tan@intel.com \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=luobin9@huawei.com \
--cc=martin.petersen@oracle.com \
--cc=maz@kernel.org \
--cc=mingo@kernel.org \
--cc=minlei@redhat.com \
--cc=mtosatti@redhat.com \
--cc=mustafa.ismail@intel.com \
--cc=netdev@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=nilal@redhat.com \
--cc=nitesh@redhat.com \
--cc=peterz@infradead.org \
--cc=pjwaskiewicz@gmail.com \
--cc=poros@redhat.com \
--cc=robin.murphy@arm.com \
--cc=rostedt@goodmis.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=saeedm@nvidia.com \
--cc=sassmann@redhat.com \
--cc=sathya.prakash@broadcom.com \
--cc=sfr@canb.auug.org.au \
--cc=shiraz.saleem@intel.com \
--cc=shivasharan.srikanteshwara@broadcom.com \
--cc=somnath.kotur@broadcom.com \
--cc=sreekanth.reddy@broadcom.com \
--cc=sriharsha.basavapatna@broadcom.com \
--cc=stephen@networkplumber.org \
--cc=suganath-prabu.subramani@broadcom.com \
--cc=sumit.saxena@broadcom.com \
--cc=tariqt@nvidia.com \
--cc=tatyana.e.nikolova@intel.com \
--cc=tglx@linutronix.de \
--cc=thenzl@redhat.com \
--cc=viresh.kumar@linaro.org \
--cc=yongqiang.niu@mediatek.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;
as well as URLs for NNTP newsgroup(s).