From: James Bottomley <James.Bottomley@steeleye.com>
To: Patrick Mansfield <patmans@us.ibm.com>
Cc: Christoph Hellwig <hch@lst.de>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] fixes and cleanups for the new command allocation code
Date: 05 Feb 2003 09:22:18 -0600 [thread overview]
Message-ID: <1044458540.1807.19.camel@mulgrave> (raw)
In-Reply-To: <20030204211516.A30419@beaverton.ibm.com>
On Tue, 2003-02-04 at 23:15, Patrick Mansfield wrote:
> OK that sounds great, except we should not plug the queue since we
> have outstanding IO.
Yes, that's true. The guaranteed returning I/O will restart it.
> > And the slave_{alloc,configure,destroy} needs fixing too.
>
> What is broken?
This one, I'm not sure. The patch just drew my attention to the
breakage. The way I understand the API:
slave_alloc tells the LLD we're going to issue probes to the device
slave_configure tells the LLD we've probed it and we're now going to
configure and use it
slave_destroy tells the LLD we're no longer interested.
The patch removes the slave_configure call from scsi_slave_attach()
which is called by the upper level drivers. However, it looks like
scsi_add_lun always calls it.
The correct thing, I think, is not to call slave_configure until we're
sure an ULD is attaching (there's no point getting the LLD to allocate
resources to a command queue until we have an attachment).
James
next prev parent reply other threads:[~2003-02-05 15:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 15:23 [PATCH] fixes and cleanups for the new command allocation code Christoph Hellwig
2003-02-04 16:16 ` Patrick Mansfield
2003-02-04 16:51 ` Christoph Hellwig
2003-02-04 17:19 ` Patrick Mansfield
2003-02-04 17:57 ` Luben Tuikov
2003-02-04 18:03 ` Christoph Hellwig
2003-02-04 18:08 ` Luben Tuikov
2003-02-04 18:33 ` James Bottomley
2003-02-04 19:29 ` Christoph Hellwig
2003-02-04 23:03 ` James Bottomley
2003-02-05 1:25 ` Patrick Mansfield
2003-02-05 1:53 ` James Bottomley
2003-02-05 5:15 ` Patrick Mansfield
2003-02-05 15:22 ` James Bottomley [this message]
2003-02-05 15:59 ` James Bottomley
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=1044458540.1807.19.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=hch@lst.de \
--cc=linux-scsi@vger.kernel.org \
--cc=patmans@us.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.