From: Christoph Hellwig <hch@infradead.org>
To: "Stephen M. Cameron" <scameron@beardog.cce.hp.com>
Cc: james.bottomley@parallels.com, webb.scales@hp.com,
martin.petersen@oracle.com, linux-scsi@vger.kernel.org,
justin.lindley@hp.com, stephenmcameron@gmail.com,
joseph.t.handzik@hp.com, thenzl@redhat.com,
michael.miller@canonical.com, scott.teel@hp.com, hch@lst.de,
dan.carpenter@oracle.com, linux-pci@vger.kernel.org
Subject: Re: [PATCH 2 08/24] hpsa: choose number of reply queues more intelligently.
Date: Mon, 2 Jun 2014 02:27:51 -0700 [thread overview]
Message-ID: <20140602092751.GA30545@infradead.org> (raw)
In-Reply-To: <20140529155302.8180.17597.stgit@beardog.cce.hp.com>
On Thu, May 29, 2014 at 10:53:02AM -0500, Stephen M. Cameron wrote:
> From: Stephen M. Cameron <scameron@beardog.cce.hp.com>
>
> No sense having 8 or 16 reply queues if you only have 4 cpus,
> and likewise no sense limiting to 8 reply queues if you have
> many more cpus.
I've applied this as it looks good as-is, but shouldn't we also
cap the number of MSI-X vectors in common code so that we avoid
adding this as boilerplate code to lots of drivers?
>
> Signed-off-by: Stephen M. Cameron <scameron@beardog.cce.hp.com>
> Reviewed-by: Mike Miller <michael.miller@canonical.com>
> Reviewed-by: Scott Teel <scott.teel@hp.com>
> ---
> drivers/scsi/hpsa.c | 2 ++
> drivers/scsi/hpsa_cmd.h | 2 +-
> 2 files changed, 3 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/scsi/hpsa.c b/drivers/scsi/hpsa.c
> index b1ecfd8..b903e86 100644
> --- a/drivers/scsi/hpsa.c
> +++ b/drivers/scsi/hpsa.c
> @@ -6157,6 +6157,8 @@ static void hpsa_interrupt_mode(struct ctlr_info *h)
> if (pci_find_capability(h->pdev, PCI_CAP_ID_MSIX)) {
> dev_info(&h->pdev->dev, "MSIX\n");
> h->msix_vector = MAX_REPLY_QUEUES;
> + if (h->msix_vector > num_online_cpus())
> + h->msix_vector = num_online_cpus();
> err = pci_enable_msix(h->pdev, hpsa_msix_entries,
> h->msix_vector);
> if (err > 0) {
> diff --git a/drivers/scsi/hpsa_cmd.h b/drivers/scsi/hpsa_cmd.h
> index db89245..104b67b 100644
> --- a/drivers/scsi/hpsa_cmd.h
> +++ b/drivers/scsi/hpsa_cmd.h
> @@ -615,7 +615,7 @@ struct TransTable_struct {
> u32 RepQCount;
> u32 RepQCtrAddrLow32;
> u32 RepQCtrAddrHigh32;
> -#define MAX_REPLY_QUEUES 8
> +#define MAX_REPLY_QUEUES 64
> struct vals32 RepQAddr[MAX_REPLY_QUEUES];
> };
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-scsi" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
---end quoted text---
next parent reply other threads:[~2014-06-02 9:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20140529154739.8180.50710.stgit@beardog.cce.hp.com>
[not found] ` <20140529155302.8180.17597.stgit@beardog.cce.hp.com>
2014-06-02 9:27 ` Christoph Hellwig [this message]
2014-06-02 14:52 ` [PATCH 2 08/24] hpsa: choose number of reply queues more intelligently scameron
2014-06-02 15:00 ` scameron
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=20140602092751.GA30545@infradead.org \
--to=hch@infradead.org \
--cc=dan.carpenter@oracle.com \
--cc=hch@lst.de \
--cc=james.bottomley@parallels.com \
--cc=joseph.t.handzik@hp.com \
--cc=justin.lindley@hp.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=michael.miller@canonical.com \
--cc=scameron@beardog.cce.hp.com \
--cc=scott.teel@hp.com \
--cc=stephenmcameron@gmail.com \
--cc=thenzl@redhat.com \
--cc=webb.scales@hp.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).