hpsa: choose number of reply queues more intelligently.
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. 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> Signed-off-by: Christoph Hellwig <hch@lst.de>
This commit is contained in:
parent
7b9235ee19
commit
f89439bc2e
2 changed files with 3 additions and 1 deletions
|
@ -6164,6 +6164,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) {
|
||||
|
|
|
@ -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];
|
||||
};
|
||||
|
||||
|
|
Loading…
Reference in a new issue