From: James Bottomley <jejb@linux.vnet.ibm.com>
To: Hannes Reinecke <hare@suse.de>,
Johannes Thumshirn <jthumshirn@suse.de>,
"Martin K . Petersen" <martin.petersen@oracle.com>
Cc: Michael Reed <mdr@sgi.com>, Laura Abbott <labbott@redhat.com>,
Laurence Oberman <loberman@redhat.com>,
Lee Duncan <lduncan@suse.com>,
Linux SCSI Mailinglist <linux-scsi@vger.kernel.org>,
stable@vger.kernel.org, #@suse.de, v4.4@suse.de
Subject: Re: [PATCH v5] qla1280: Don't allocate 512kb of host tags
Date: Wed, 27 Apr 2016 13:09:35 -0700 [thread overview]
Message-ID: <1461787775.2311.40.camel@linux.vnet.ibm.com> (raw)
In-Reply-To: <572096C4.4090705@suse.de>
On Wed, 2016-04-27 at 12:39 +0200, Hannes Reinecke wrote:
> On 04/27/2016 10:48 AM, Johannes Thumshirn wrote:
> > The qla1280 driver sets the scsi_host_template's can_queue field to
> > 0xfffff
> > which results in an allocation failure when allocating the block
> > layer tags
> > for the driver's queues. This was introduced with the change for
> > host wide
> > tags in commit 64d513ac31b - "scsi: use host wide tags by default".
> >
> > Reduce can_queue to MAX_OUTSTANDING_COMMANDS (512) to solve the
> > allocation
> > error.
> >
> > Signed-off-by: Johannes Thumshirn <jthumshirn@suse.de>
> > Fixes: 64d513ac31b - "scsi: use host wide tags by default"
> > Cc: stable@vger.kernel.org # v4.4
> > Cc: Laura Abbott <labbott@redhat.com>
> > Cc: Michael Reed <mdr@sgi.com>
> > Reviewed-by: Laurence Oberman <loberman@redhat.com>
> > Reviewed-by: Lee Duncan <lduncan@suse.com>
> > ---
> > Changes to v4:
> > * Make subject more meaningfull
> > * Remove warning's backtrace
> > * Re-add reference to commit 64d513ac31b - "scsi: use host wide
> > tags by default"
> >
> > Changes to v3:
> > * Use MAX_OUTSTANDING_COMMANDS insted of hard coded magical number
> >
> > Changes to v2:
> > * Change can_queue to 512 upon James' request
> >
> > drivers/scsi/qla1280.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/scsi/qla1280.c b/drivers/scsi/qla1280.c
> > index 5d0ec42..634254a 100644
> > --- a/drivers/scsi/qla1280.c
> > +++ b/drivers/scsi/qla1280.c
> > @@ -4214,7 +4214,7 @@ static struct scsi_host_template
> > qla1280_driver_template = {
> > .eh_bus_reset_handler = qla1280_eh_bus_reset,
> > .eh_host_reset_handler = qla1280_eh_adapter_reset,
> > .bios_param = qla1280_biosparam,
> > - .can_queue = 0xfffff,
> > + .can_queue = MAX_OUTSTANDING_COMMANDS,
> > .this_id = -1,
> > .sg_tablesize = SG_ALL,
> > .use_clustering = ENABLE_CLUSTERING,
> >
> Hmm.
>
> The driver has this:
>
> ha->request_ring = pci_alloc_consistent(ha->pdev,
> ((REQUEST_ENTRY_CNT + 1) * sizeof(request_t)),
> &ha->request_dma);
>
> and
>
> /* ISP request and response entry counts (37-65535) */
> #define REQUEST_ENTRY_CNT 255 /* Number of request entries. */
> #define RESPONSE_ENTRY_CNT 63 /* Number of response entries.
> */
>
> IE the driver (as it stands currently) will never be able to queue
> more than 255 requests.
> So where's the point in setting can_queue to 512? Shouldn't we
> rather use 255 here?
Because that's for the request/response message ring. You don't keep a
request allocated while the command is outstanding, you send a request
message with the command handle (the index into the outstanding_cmds
array) and a pointer to the command and get a response back when the
firmware accepts it (at which time you can re-use the request).
You eventually get a completion interrupt with MBA_SCSI_COMPLETION and
a handle number (index into the outstanding_cmds array) when the host
is done with the command.
James
next prev parent reply other threads:[~2016-04-27 20:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-27 8:48 [PATCH v5] qla1280: Don't allocate 512kb of host tags Johannes Thumshirn
2016-04-27 10:39 ` Hannes Reinecke
2016-04-27 20:09 ` James Bottomley [this message]
2016-04-30 0:28 ` Martin K. Petersen
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=1461787775.2311.40.camel@linux.vnet.ibm.com \
--to=jejb@linux.vnet.ibm.com \
--cc=#@suse.de \
--cc=hare@suse.de \
--cc=jthumshirn@suse.de \
--cc=labbott@redhat.com \
--cc=lduncan@suse.com \
--cc=linux-scsi@vger.kernel.org \
--cc=loberman@redhat.com \
--cc=martin.petersen@oracle.com \
--cc=mdr@sgi.com \
--cc=stable@vger.kernel.org \
--cc=v4.4@suse.de \
/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).