From: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
To: "Saleem, Shiraz" <shiraz.saleem@intel.com>
Cc: "Ismail, Mustafa" <mustafa.ismail@intel.com>,
"Bednarz, Christopher N" <christopher.n.bednarz@intel.com>,
"Barrera, Ivan D" <ivan.d.barrera@intel.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [net-next] irdma: change name of interrupts
Date: Tue, 15 Nov 2022 13:47:35 +0100 [thread overview]
Message-ID: <Y3OKZx8eAj3KwHB9@localhost.localdomain> (raw)
In-Reply-To: <MWHPR11MB002973559040490B1377165BE9059@MWHPR11MB0029.namprd11.prod.outlook.com>
On Mon, Nov 14, 2022 at 04:19:20PM +0000, Saleem, Shiraz wrote:
> > Subject: [net-next] irdma: change name of interrupts
> >
>
> This cant go through net-next. It needs to go through the rdma tree. I will co-ordinate w. Tony on it.
>
> Use "RDMA/irdma: change name of interrupts" for the subject.
>
I will remember, is "rdma" the name of tree?
> > Add more information in interrupt names.
> >
> > Before this patch it was:
> > irdma
> > CEQ
> > CEQ
> > ...
> >
> > Now:
> > irdma-ice-AEQ
> > irdma-ice-CEQ-0
> > irdma-ice-CEQ-1
>
> This is better for sure. But we need to add the device name. Not sure if adding "ice" is adding any value.
>
> Ideally, for the RDMA drivers, this should be ib_device name. But there is a limitation in RDMA subsystem that doesn't
> set the name till after the ib device is registered which happens later in the drv.probe() flow.
>
> So I think our best option is to use the PCI device name.
>
Sure, will change it, thanks.
> > ...
> >
> > Signed-off-by: Michal Swiatkowski <michal.swiatkowski@linux.intel.com>
> > Suggested-by: Piotr Raczynski <piotr.raczynski@intel.com>
> > ---
> > drivers/infiniband/hw/irdma/defs.h | 2 ++
> > drivers/infiniband/hw/irdma/hw.c | 14 +++++++++++---
> > drivers/infiniband/hw/irdma/main.h | 1 +
> > 3 files changed, 14 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/infiniband/hw/irdma/defs.h b/drivers/infiniband/hw/irdma/defs.h
> > index c1906cab5c8a..09e4aba31b64 100644
> > --- a/drivers/infiniband/hw/irdma/defs.h
> > +++ b/drivers/infiniband/hw/irdma/defs.h
> > @@ -20,6 +20,8 @@
> > #define IRDMA_IRD_HW_SIZE_128 3
> > #define IRDMA_IRD_HW_SIZE_256 4
> >
> > +#define IRDMA_INT_NAME_STR_LEN (32)
>
> INT to IRQ which is more used in this driver to reflect interrupt. Drop the (). And move to this main.h where the irdma_msix_vector struct is defined.
>
Done
> > +
> > enum irdma_protocol_used {
> > IRDMA_ANY_PROTOCOL = 0,
> > IRDMA_IWARP_PROTOCOL_ONLY = 1,
> > diff --git a/drivers/infiniband/hw/irdma/hw.c b/drivers/infiniband/hw/irdma/hw.c
> > index ab246447520b..46665624e515 100644
> > --- a/drivers/infiniband/hw/irdma/hw.c
> > +++ b/drivers/infiniband/hw/irdma/hw.c
> > @@ -1087,14 +1087,20 @@ static int irdma_cfg_ceq_vector(struct irdma_pci_f *rf,
> > struct irdma_ceq *iwceq,
> > int status;
> >
> > if (rf->msix_shared && !ceq_id) {
> > + snprintf(msix_vec->name, sizeof(msix_vec->name) - 1,
> > + "irdma-%s-AEQCEQ-%d",
> > + dev_driver_string(&rf->pcidev->dev), ceq_id);
>
> As per previous comment, I think dev_name((&rf->pcidev->dev) is better. Given this should we make the msix_vec.name be a 64b variable?
>
Yeah, it looks better, thanks. I changed name to 64b.
> Shiraz
>
>
_______________________________________________
Intel-wired-lan mailing list
Intel-wired-lan@osuosl.org
https://lists.osuosl.org/mailman/listinfo/intel-wired-lan
prev parent reply other threads:[~2022-11-15 12:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-14 8:20 [Intel-wired-lan] [net-next] irdma: change name of interrupts Michal Swiatkowski
2022-11-14 16:19 ` Saleem, Shiraz
2022-11-15 12:47 ` Michal Swiatkowski [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=Y3OKZx8eAj3KwHB9@localhost.localdomain \
--to=michal.swiatkowski@linux.intel.com \
--cc=christopher.n.bednarz@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivan.d.barrera@intel.com \
--cc=mustafa.ismail@intel.com \
--cc=shiraz.saleem@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