From: Doug Ledford <dledford@redhat.com>
To: Tony Battersby <tonyb@cybernetics.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: ide-scsi cmd_per_lun
Date: Tue, 9 Jul 2002 18:00:14 -0400 [thread overview]
Message-ID: <20020709180014.A12706@redhat.com> (raw)
In-Reply-To: <000701c2278e$2dc723a0$e0019d89@cybernetics.com>; from tonyb@cybernetics.com on Tue, Jul 09, 2002 at 05:18:31PM -0400
On Tue, Jul 09, 2002 at 05:18:31PM -0400, Tony Battersby wrote:
>
> The problem boils down to the fact that ide-scsi relies on the mid-level
> (old eh) to do the auto-sense. I was able to work around this problem by
> setting cmd_per_lun: 1 in ide-scsi.h (vanilla 2.4.17). Doing this caused
> the request sense command to make it to the drive before any other command
> could sneak in and reset the sense data. Can anyone tell me if this is a
> good solution?
It is the appropriate setting for any driver that doesn't automatically
request sense itself on check condition status returns. It does not solve
the problem for tagged queue enabled devices though since they don't honor
this field and will loose sense information, so in reality any driver that
doesn't auto request sense data is broken to some extent. The new eh code
requires that drivers auto request sense, so this is actually likely to be
really broken in 2.5 at the moment since the old eh code is now gone.
> Looking at the 2.4.19-rc1 source, I see an additional field
> "can_queue: 10" in the template. Should this be changed too? I cannot use
> 2.4.19 for the moment, so I can't experiment with it.
No, this is only for the host wide queue, so if you had 5 ide-scsi devices
that showed up, this limits the total number of commands sent to the
ide-scsi driver to 10, which would be 2 each. Obviously, this is
different than what you are trying to set and is only limited by what the
ide-scsi driver can actually handle in terms of outstanding commands at a
time.
>
> Thanks,
> Anthony J. Battersby
> Cybernetics
>
> -
> 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
--
Doug Ledford <dledford@redhat.com> 919-754-3700 x44233
Red Hat, Inc.
1801 Varsity Dr.
Raleigh, NC 27606
prev parent reply other threads:[~2002-07-09 22:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-09 21:18 ide-scsi cmd_per_lun Tony Battersby
2002-07-09 22:00 ` Doug Ledford [this message]
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=20020709180014.A12706@redhat.com \
--to=dledford@redhat.com \
--cc=linux-scsi@vger.kernel.org \
--cc=tonyb@cybernetics.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