On Fri, Oct 4, 2013 at 5:18 AM, Ewan Milne wrote:
> On Thu, 2013-10-03 at 13:48 -0700, Eric Seppanen wrote:
>> Do I/O timeouts and flush timeouts need to be independently adjusted?
>> If you're having trouble with slow operations, it seems likely to be
>> across the board.
>>
>> Flush timeout coul
x-ker...@vger.kernel.org;
> > de...@linuxdriverproject.org;
> > linux-scsi@vger.kernel.org
> > Subject: Re: Drivers: scsi: FLUSH timeout
> >
> > On Thu, Oct 3, 2013 at 5:09 AM, Nicholas A. Bellinger
> > wrote:
> > >
> > > On Wed, 2013-10-02 at 18:29 +,
> -Original Message-
> From: Eric Seppanen [mailto:e...@purestorage.com]
> Sent: Thursday, October 03, 2013 1:49 PM
> To: Nicholas A. Bellinger
> Cc: KY Srinivasan; linux-ker...@vger.kernel.org; de...@linuxdriverproject.org;
> linux-scsi@vger.kernel.org
> Subje
On Thu, 2013-10-03 at 13:48 -0700, Eric Seppanen wrote:
> On Thu, Oct 3, 2013 at 5:09 AM, Nicholas A. Bellinger
> wrote:
> >
> > On Wed, 2013-10-02 at 18:29 +, KY Srinivasan wrote:
> > > Ideally, I want this to be adjustable like the way we can change the I/O
> > > timeout.
> > > Since that h
On Thu, Oct 3, 2013 at 5:09 AM, Nicholas A. Bellinger
wrote:
>
> On Wed, 2013-10-02 at 18:29 +, KY Srinivasan wrote:
> > Ideally, I want this to be adjustable like the way we can change the I/O
> > timeout.
> > Since that has been attempted earlier and rejected (not clear what the
> > reason
; oher...@suse.com;
> jbottom...@parallels.com; h...@infradead.org; linux-scsi@vger.kernel.org
> Subject: Re: Drivers: scsi: FLUSH timeout
>
> On Wed, 2013-10-02 at 18:29 +, KY Srinivasan wrote:
> >
> > > -Original Message-
> > > From: geert.uytterh
Srinivasan
> > Cc: Mike Christie; Jack Wang; Greg KH; linux-ker...@vger.kernel.org;
> > de...@linuxdriverproject.org; oher...@suse.com; jbottom...@parallels.com;
> > h...@infradead.org; linux-scsi@vger.kernel.org
> > Subject: Re: Drivers: scsi: FLUSH timeout
> >
> &g
Srinivasan
> > Cc: Mike Christie; Jack Wang; Greg KH; linux-ker...@vger.kernel.org;
> > de...@linuxdriverproject.org; oher...@suse.com; jbottom...@parallels.com;
> > h...@infradead.org; linux-scsi@vger.kernel.org
> > Subject: Re: Drivers: scsi: FLUSH timeout
> >
> &g
r.kernel.org;
> de...@linuxdriverproject.org; oher...@suse.com; jbottom...@parallels.com;
> h...@infradead.org; linux-scsi@vger.kernel.org
> Subject: Re: Drivers: scsi: FLUSH timeout
>
> On Tue, Sep 24, 2013 at 11:53 PM, KY Srinivasan wrote:
> > I am not sure how that magic number was arrived
On Tue, Sep 24, 2013 at 11:53 PM, KY Srinivasan wrote:
> I am not sure how that magic number was arrived at (the 60HZ number). We want
> this to be little higher -
"60 * HZ" means "60 seconds".
> would there be any issues raising this to say 180 seconds. This is the value
> we currently have
parallels.com;
> h...@infradead.org; linux-scsi@vger.kernel.org
> Subject: Re: Drivers: scsi: FLUSH timeout
>
> On 09/24/2013 07:35 AM, KY Srinivasan wrote:
> >
> >
> >> -Original Message-
> >> From: Jack Wang [mailto:xjtu...@gmail.com]
> >> Sent: Tuesda
ct.org;
>> oher...@suse.com; jbottom...@parallels.com; h...@infradead.org; linux-
>> s...@vger.kernel.org; Mike Christie
>> Subject: Re: Drivers: scsi: FLUSH timeout
>>
>> On 09/21/2013 07:24 AM, KY Srinivasan wrote:
>>>
>>>
>>>> ---
...@infradead.org; linux-
s...@vger.kernel.org; Mike Christie
Subject: Re: Drivers: scsi: FLUSH timeout
On 09/21/2013 07:24 AM, KY Srinivasan wrote:
-Original Message-
From: Greg KH [mailto:gre...@linuxfoundation.org]
Sent: Friday, September 20, 2013 1:32 PM
To: KY Srinivasan
Cc: linux
ad.org; linux-
> s...@vger.kernel.org; Mike Christie
> Subject: Re: Drivers: scsi: FLUSH timeout
>
> On 09/21/2013 07:24 AM, KY Srinivasan wrote:
> >
> >
> >> -Original Message-
> >> From: Greg KH [mailto:gre...@linuxfoundation.org]
> >> Sent: Fri
ct.org;
>> oher...@suse.com; jbottom...@parallels.com; h...@infradead.org; linux-
>> s...@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 curr
ad.org; linux-
> s...@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:
I am thinking Srini meant in the sd_mod driver module.
#define SD_FLUSH_TIMEOUT (60 * HZ)
Laurence
On Fri, Sep 20, 2013 at 4:32 PM, Greg KH wrote:
> On Fri, Sep 20, 2013 at 12:32:27PM -0700, K. Y. Srinivasan wrote:
>> The SD_FLUSH_TIMEOUT value is currently hardcoded.
>
> Hardcoded where? Plea
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.
> 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 se
The SD_FLUSH_TIMEOUT value is currently hardcoded. 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.
Regards,
K. Y
--
To unsubscribe from this list: send the line "unsubscribe linux-scsi"
19 matches
Mail list logo
