public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Tejun Heo <htejun@gmail.com>
To: Kai Makisara <Kai.Makisara@kolumbus.fi>
Cc: James Bottomley <James.Bottomley@SteelEye.com>,
	linux-scsi@vger.kernel.org
Subject: Re: [PATCH RESEND 1/2] SCSI: use scsi_device->timeout consistently
Date: Mon, 20 Nov 2006 08:26:29 +0900	[thread overview]
Message-ID: <4560E825.3080504@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0611192353590.4946@kai.makisara.local>

Kai Makisara wrote:
> On Sun, 19 Nov 2006, Tejun Heo wrote:
> 
>> Each high level driver uses scsi_device->timeout diffrently.
>>
> ...
>> Index: scsi-misc-2.6/drivers/scsi/st.c
>> ===================================================================
>> --- scsi-misc-2.6.orig/drivers/scsi/st.c
>> +++ scsi-misc-2.6/drivers/scsi/st.c
>> @@ -3986,7 +3986,8 @@ static int st_probe(struct device *dev)
>>  	tpnt->partition = 0;
>>  	tpnt->new_partition = 0;
>>  	tpnt->nbr_partitions = 0;
>> -	tpnt->device->timeout = ST_TIMEOUT;
>> +	if (!SDp->timeout)
>> +		SDp->timeout = ST_TIMEOUT;
> 
> I don't think this should be done. It probably makes the default timeout 
> way too short. The error recovery with tapes takes a long time. The user 
> can change the timeout if the default (900 seconds) seems too long (or 
> short).
> 
> I don't think there is anything in the midlevel or low-level code to set 
> the timeout based on the device characteristics. This is left to the ULD.

Low level driver should configure timeout or retries to a known value 
iff it knows what it's doing, when it knows both transport and 
device-type specific characteristic.  AFAICS, the only driver which 
modifies sdev->timeout is ipr and it does so only when it knows the 
device is of certain type.  So, I don't think it will cause any trouble, 
and using different initialization in different ULDs is too subtle.

Thanks.

-- 
tejun

  reply	other threads:[~2006-11-19 23:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-19 12:51 [PATCH RESEND 1/2] SCSI: use scsi_device->timeout consistently Tejun Heo
2006-11-19 12:52 ` [PATCH RESEND 2/2] SCSI: add scsi_device->retries Tejun Heo
2006-11-19 22:32   ` Kai Makisara
2006-11-19 23:31     ` Tejun Heo
2006-11-20 21:42       ` Kai Makisara
2006-11-19 22:01 ` [PATCH RESEND 1/2] SCSI: use scsi_device->timeout consistently Kai Makisara
2006-11-19 23:26   ` Tejun Heo [this message]
2006-11-20 21:25     ` Kai Makisara
2006-11-21  2:14       ` Tejun Heo

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=4560E825.3080504@gmail.com \
    --to=htejun@gmail.com \
    --cc=James.Bottomley@SteelEye.com \
    --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