From: James Bottomley <James.Bottomley@SteelEye.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: [PATCH] tmscsim: scsi device attributes
Date: 22 Oct 2004 09:00:11 -0400 [thread overview]
Message-ID: <1098450017.2017.19.camel@mulgrave> (raw)
In-Reply-To: <20041022124007.GC4201@parcelfarce.linux.theplanet.co.uk>
On Fri, 2004-10-22 at 08:40, Matthew Wilcox wrote:
> How about something more along the following lines? I haven't converted
> sym2 to the generic queue code yet, so it's untested (and is obviously
> broken because nothing initialises max_queue_depth).
Yes, I was considering something like this. The original queue code in
53c700 was designed as an example of how to do attribute overrides.
However, there needs to be a callback into the LLD to tell it that the
queue is being overriden (and allow a veto for depth increases). I'll
look at adding the extra pieces.
James
next prev parent reply other threads:[~2004-10-22 13:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 20:31 [PATCH] tmscsim: scsi device attributes Guennadi Liakhovetski
2004-10-22 12:40 ` Matthew Wilcox
2004-10-22 13:00 ` James Bottomley [this message]
2004-10-22 19:27 ` Guennadi Liakhovetski
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=1098450017.2017.19.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-scsi@vger.kernel.org \
--cc=matthew@wil.cx \
/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