From: Jack Wang <xjtuwjp@gmail.com>
To: KY Srinivasan <kys@microsoft.com>
Cc: Greg KH <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devel@linuxdriverproject.org" <devel@linuxdriverproject.org>,
"ohering@suse.com" <ohering@suse.com>,
"jbottomley@parallels.com" <jbottomley@parallels.com>,
"hch@infradead.org" <hch@infradead.org>,
"linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
Mike Christie <michaelc@cs.wisc.edu>
Subject: Re: Drivers: scsi: FLUSH timeout
Date: Tue, 24 Sep 2013 14:08:23 +0200 [thread overview]
Message-ID: <524180B7.7090307@gmail.com> (raw)
In-Reply-To: <a97d266e2c284d688d2dd7ad43f179b8@SN2PR03MB061.namprd03.prod.outlook.com>
On 09/21/2013 07:24 AM, KY Srinivasan wrote:
>
>
>> -----Original Message-----
>> From: Greg KH [mailto:gregkh@linuxfoundation.org]
>> Sent: Friday, September 20, 2013 1:32 PM
>> To: KY Srinivasan
>> Cc: linux-kernel@vger.kernel.org; devel@linuxdriverproject.org;
>> ohering@suse.com; jbottomley@parallels.com; hch@infradead.org; linux-
>> scsi@vger.kernel.org
>> Subject: Re: Drivers: scsi: FLUSH timeout
>>
>> On Fri, Sep 20, 2013 at 12:32:27PM -0700, K. Y. Srinivasan wrote:
>>> The SD_FLUSH_TIMEOUT value is currently hardcoded.
>>
>> Hardcoded where? Please, more context.
>
> This is defined in scsi/sd.h:
>
> #define SD_FLUSH_TIMEOUT (60 * HZ)
>>
>>> On our cloud, we sometimes hit this timeout. I was wondering if we
>>> could make this a module parameter. If this is acceptable, I can send
>>> you a patch for this.
>>
>> A module parameter don't make sense for a per-device value, does it?
> Currently, the 60 second timeout is applied across devices. Ideally, I want to be
> able to control the FLUSH TIMEOUT as we currently do I/O timeout. If this is
> acceptable, I can work on a patch for that as well.
>
> Regards,
>
> K. Y
>>
>> greg k-h
> --
> 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
>
Hi,
Back to 2010, Mike(cc-ed) try to add a flush time out interface, similar
to what you want here, no idea why it's just ignored?
http://www.spinics.net/lists/linux-scsi/msg45017.html
Jack
next prev parent reply other threads:[~2013-09-24 12:08 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-20 19:32 Drivers: scsi: FLUSH timeout K. Y. Srinivasan
2013-09-20 20:32 ` Greg KH
2013-09-20 21:00 ` Laurence Oberman
2013-09-21 5:24 ` KY Srinivasan
2013-09-24 12:08 ` Jack Wang [this message]
2013-09-24 12:35 ` KY Srinivasan
2013-09-24 13:10 ` Bernd Schubert
2013-09-24 17:20 ` Mike Christie
2013-09-24 21:53 ` KY Srinivasan
2013-09-25 8:40 ` Geert Uytterhoeven
2013-10-02 18:29 ` KY Srinivasan
2013-10-03 12:09 ` Nicholas A. Bellinger
2013-10-03 14:13 ` KY Srinivasan
2013-10-03 20:48 ` Eric Seppanen
2013-10-04 12:18 ` Ewan Milne
2013-10-04 18:12 ` Eric Seppanen
2013-10-04 15:02 ` KY Srinivasan
2013-10-04 16:27 ` James Bottomley
2013-10-03 14:01 ` 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=524180B7.7090307@gmail.com \
--to=xjtuwjp@gmail.com \
--cc=devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=hch@infradead.org \
--cc=jbottomley@parallels.com \
--cc=kys@microsoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
--cc=ohering@suse.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;
as well as URLs for NNTP newsgroup(s).