Message ID | 20210903152430.244937-1-nitesh@redhat.com (mailing list archive) |
---|---|
Headers | show |
Series | genirq: Cleanup the abuse of irq_set_affinity_hint() | expand |
On Fri, Sep 3, 2021 at 11:25 AM Nitesh Narayan Lal <nitesh@redhat.com> wrote: > > The drivers currently rely on irq_set_affinity_hint() to either set the > affinity_hint that is consumed by the userspace and/or to enforce a custom > affinity. > > irq_set_affinity_hint() as the name suggests is originally introduced to > only set the affinity_hint to help the userspace in guiding the interrupts > and not the affinity itself. However, since the commit > > e2e64a932556 "genirq: Set initial affinity in irq_set_affinity_hint()" [...] > > Nitesh Narayan Lal (13): > iavf: Use irq_update_affinity_hint > i40e: Use irq_update_affinity_hint > scsi: megaraid_sas: Use irq_set_affinity_and_hint > scsi: mpt3sas: Use irq_set_affinity_and_hint > RDMA/irdma: Use irq_update_affinity_hint > enic: Use irq_update_affinity_hint > be2net: Use irq_update_affinity_hint > ixgbe: Use irq_update_affinity_hint > mailbox: Use irq_update_affinity_hint > scsi: lpfc: Use irq_set_affinity > hinic: Use irq_set_affinity_and_hint > net/mlx5: Use irq_set_affinity_and_hint > net/mlx4: Use irq_update_affinity_hint > > Thomas Gleixner (1): > genirq: Provide new interfaces for affinity hints > Any suggestions on what should be the next steps here? Unfortunately, I haven't been able to get any reviews on the following two patches: be2net: Use irq_update_affinity_hint hinic: Use irq_set_affinity_and_hint One option would be to proceed with the remaining patches and I can try posting these two again when I post patches for the remaining drivers?
Nitesh, On Mon, Sep 13 2021 at 10:34, Nitesh Lal wrote: > On Fri, Sep 3, 2021 at 11:25 AM Nitesh Narayan Lal <nitesh@redhat.com> wrote: >> >> The drivers currently rely on irq_set_affinity_hint() to either set the >> affinity_hint that is consumed by the userspace and/or to enforce a custom >> affinity. >> >> irq_set_affinity_hint() as the name suggests is originally introduced to >> only set the affinity_hint to help the userspace in guiding the interrupts >> and not the affinity itself. However, since the commit >> >> e2e64a932556 "genirq: Set initial affinity in irq_set_affinity_hint()" sorry for ignoring this. It fell through the cracks. >> Thomas Gleixner (1): >> genirq: Provide new interfaces for affinity hints Did I actually write this? > Any suggestions on what should be the next steps here? Unfortunately, I haven't > been able to get any reviews on the following two patches: > be2net: Use irq_update_affinity_hint > hinic: Use irq_set_affinity_and_hint > > One option would be to proceed with the remaining patches and I can try > posting these two again when I post patches for the remaining drivers? The more general question is whether I should queue all the others or whether some subsystem would prefer to pull in a tagged commit on top of rc1. I'm happy to carry them all of course. Thanks, tglx
On Wed, Nov 24, 2021 at 2:30 PM Thomas Gleixner <tglx@linutronix.de> wrote: > > Nitesh, > > On Mon, Sep 13 2021 at 10:34, Nitesh Lal wrote: > > On Fri, Sep 3, 2021 at 11:25 AM Nitesh Narayan Lal <nitesh@redhat.com> wrote: > >> > >> The drivers currently rely on irq_set_affinity_hint() to either set the > >> affinity_hint that is consumed by the userspace and/or to enforce a custom > >> affinity. > >> > >> irq_set_affinity_hint() as the name suggests is originally introduced to > >> only set the affinity_hint to help the userspace in guiding the interrupts > >> and not the affinity itself. However, since the commit > >> > >> e2e64a932556 "genirq: Set initial affinity in irq_set_affinity_hint()" > > sorry for ignoring this. It fell through the cracks. No worries, thank you for reviewing. > > > >> Thomas Gleixner (1): > >> genirq: Provide new interfaces for affinity hints > > Did I actually write this? Yeap, the idea and the initial patch came from you. :) > > > > Any suggestions on what should be the next steps here? Unfortunately, I haven't > > been able to get any reviews on the following two patches: > > be2net: Use irq_update_affinity_hint > > hinic: Use irq_set_affinity_and_hint > > > > One option would be to proceed with the remaining patches and I can try > > posting these two again when I post patches for the remaining drivers? > > The more general question is whether I should queue all the others or > whether some subsystem would prefer to pull in a tagged commit on top of > rc1. I'm happy to carry them all of course. > I am fine either way. In the past, while I was asking for more testing help I was asked if the SCSI changes are part of Martins's scsi-fixes tree as that's something Broadcom folks test to check for regression. So, maybe Martin can pull this up?
Hi Martin, On Wed, Nov 24, 2021 at 5:16 PM Nitesh Lal <nilal@redhat.com> wrote: > > On Wed, Nov 24, 2021 at 2:30 PM Thomas Gleixner <tglx@linutronix.de> wrote: > > > > Nitesh, > > > > On Mon, Sep 13 2021 at 10:34, Nitesh Lal wrote: > > > On Fri, Sep 3, 2021 at 11:25 AM Nitesh Narayan Lal <nitesh@redhat.com> wrote: > > >> > > >> The drivers currently rely on irq_set_affinity_hint() to either set the > > >> affinity_hint that is consumed by the userspace and/or to enforce a custom > > >> affinity. > > >> > > >> irq_set_affinity_hint() as the name suggests is originally introduced to > > >> only set the affinity_hint to help the userspace in guiding the interrupts > > >> and not the affinity itself. However, since the commit > > >> > > >> e2e64a932556 "genirq: Set initial affinity in irq_set_affinity_hint()" > > > > sorry for ignoring this. It fell through the cracks. > > > No worries, thank you for reviewing. > > > > > > > >> Thomas Gleixner (1): > > >> genirq: Provide new interfaces for affinity hints > > > > Did I actually write this? > > > Yeap, the idea and the initial patch came from you. :) > > > > > > > > Any suggestions on what should be the next steps here? Unfortunately, I haven't > > > been able to get any reviews on the following two patches: > > > be2net: Use irq_update_affinity_hint > > > hinic: Use irq_set_affinity_and_hint > > > > > > One option would be to proceed with the remaining patches and I can try > > > posting these two again when I post patches for the remaining drivers? > > > > The more general question is whether I should queue all the others or > > whether some subsystem would prefer to pull in a tagged commit on top of > > rc1. I'm happy to carry them all of course. > > > > I am fine either way. > In the past, while I was asking for more testing help I was asked if the > SCSI changes are part of Martins's scsi-fixes tree as that's something > Broadcom folks test to check for regression. > So, maybe Martin can pull this up? > Gentle ping. Any thoughts on the above query?
On Fri, Dec 10 2021 at 08:51, Nitesh Lal wrote: > On Wed, Nov 24, 2021 at 5:16 PM Nitesh Lal <nilal@redhat.com> wrote: >> > The more general question is whether I should queue all the others or >> > whether some subsystem would prefer to pull in a tagged commit on top of >> > rc1. I'm happy to carry them all of course. >> > >> >> I am fine either way. >> In the past, while I was asking for more testing help I was asked if the >> SCSI changes are part of Martins's scsi-fixes tree as that's something >> Broadcom folks test to check for regression. >> So, maybe Martin can pull this up? >> > > Gentle ping. > Any thoughts on the above query? As nobody cares, I'll pick it up. Thanks, tglx
On Fri, Dec 10, 2021 at 1:44 PM Thomas Gleixner <tglx@linutronix.de> wrote: > > On Fri, Dec 10 2021 at 08:51, Nitesh Lal wrote: > > On Wed, Nov 24, 2021 at 5:16 PM Nitesh Lal <nilal@redhat.com> wrote: > >> > The more general question is whether I should queue all the others or > >> > whether some subsystem would prefer to pull in a tagged commit on top of > >> > rc1. I'm happy to carry them all of course. > >> > > >> > >> I am fine either way. > >> In the past, while I was asking for more testing help I was asked if the > >> SCSI changes are part of Martins's scsi-fixes tree as that's something > >> Broadcom folks test to check for regression. > >> So, maybe Martin can pull this up? > >> > > > > Gentle ping. > > Any thoughts on the above query? > > As nobody cares, I'll pick it up. > Sounds good to me. Thank you! -- Nitesh