From: Mike Christie <michaelc@cs.wisc.edu>
To: Kai Makisara <Kai.Makisara@kolumbus.fi>
Cc: linux-scsi@vger.kernel.org
Subject: Re: [PATCH 4/5] convert st to use scsi_execte_async
Date: Sun, 18 Sep 2005 10:03:25 -0500 [thread overview]
Message-ID: <432D81BD.9080803@cs.wisc.edu> (raw)
In-Reply-To: <Pine.LNX.4.61.0509181456370.14776@kai.makisara.local>
Kai Makisara wrote:
> On Sat, 17 Sep 2005, Mike Christie wrote:
>
>
>>On Sat, 2005-09-17 at 10:55 -0500, Mike Christie wrote:
>>
>>>Mike Christie wrote:
>>>
>>>>Kai Makisara wrote:
>>>>
>>>>
>>>>>I think I may have found the problem: scsi_execute_async does not use
>>>>>the parameter retries (the same applies to scsi_execute btw). This
>>>>>leads to retrying the reads at filemark and this is not correct. I
>>>>>added the hack below to scsi_execute_async and after this the simple
>>>>>tests succeed.
>>>>
>>>>
>>>>ah ok. I think when we prep the command we need to copy the retries from
>>>>the command. So in st.c st_init_command callout we need to copy that
>>>>value (we are just copying the timeout today).
>>>
>>>oh I guess there is not retries count on the request like there is for
>>>timeout :)
>>>
>>>But it looks like retried is always 0. I guess st's init_command could
>>>just do
>>>
>>>SCpnt->allowed = 0;
>
>
> This does not work because st_init_command() is not called (called only
> with SG_IO ioctls).
The scsi_execute* functions actually send all commands down as
REQ_BLOCK_PC commands like SG_IO so we are always going through the
st_init_commad().
>
>
>>
>>Or how about this patch it was made against my updated patches here:
>>http://www.cs.wisc.edu/~michaelc/block/use-sg/v6/
>>
>>It is the 06-add-retry-field.patch patch. All it does it add a retries
>>count onto the request so it can be passed around like the timeout
>>value.
>>
>
> [patch cut]
>
> This looks like a clean approach because it allows passing the retries
> parameter of scsi_execute_* to the request processing.
>
> I tested this but it does not quite work: there are now two retries in the
> same test that previously gave six retries. Unfortunately I don't just now
> have time to study the problem further.
>
ok I will try to look into it.
next prev parent reply other threads:[~2005-09-18 17:03 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-16 4:39 [PATCH 4/5] convert st to use scsi_execte_async Mike Christie
2005-09-17 11:57 ` Kai Makisara
2005-09-17 15:43 ` Mike Christie
2005-09-17 15:55 ` Mike Christie
2005-09-17 16:25 ` Mike Christie
2005-09-18 12:01 ` Kai Makisara
2005-09-18 15:03 ` Mike Christie [this message]
2005-09-18 15:17 ` Mike Christie
2005-09-18 17:40 ` Kai Makisara
2005-09-18 15:46 ` Mike Christie
2005-09-18 16:13 ` Mike Christie
2005-09-18 16:08 ` Mike Christie
2005-09-18 16:36 ` Mike Christie
2005-09-18 16:38 ` Mike Christie
2005-09-18 19:03 ` Kai Makisara
2005-09-18 17:01 ` Mike Christie
2005-09-19 18:39 ` Kai Makisara
2005-09-19 19:22 ` Mike Christie
2005-09-20 19:23 ` Kai Makisara
2005-09-20 19:55 ` Mike Christie
2005-09-20 20:20 ` James Bottomley
2005-09-20 21:17 ` Kai Makisara
2005-09-20 22:39 ` Douglas Gilbert
2005-09-22 20:12 ` Kai Makisara
2005-09-23 3:20 ` Mike Christie
2005-09-17 15:57 ` Kai Makisara
2005-09-17 16:48 ` Kai Makisara
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=432D81BD.9080803@cs.wisc.edu \
--to=michaelc@cs.wisc.edu \
--cc=Kai.Makisara@kolumbus.fi \
--cc=linux-scsi@vger.kernel.org \
/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).