From: Geert Uytterhoeven <geert@linux-m68k.org>
To: KY Srinivasan <kys@microsoft.com>
Cc: Mike Christie <michaelc@cs.wisc.edu>,
Jack Wang <xjtuwjp@gmail.com>,
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>
Subject: Re: Drivers: scsi: FLUSH timeout
Date: Wed, 25 Sep 2013 10:40:24 +0200 [thread overview]
Message-ID: <CAMuHMdV-BsKc-c1YhzqFrUGJhw+jMZEXXTcT2xyDLnw-JQuVaQ@mail.gmail.com> (raw)
In-Reply-To: <bf168ab724a140f989ab3dfe877b750f@SN2PR03MB061.namprd03.prod.outlook.com>
On Tue, Sep 24, 2013 at 11:53 PM, KY Srinivasan <kys@microsoft.com> 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 for I/O
> timeout.
So you want to replace it by "180 * HZ", which is ... another magic number?
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2013-09-25 8:40 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
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 [this message]
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=CAMuHMdV-BsKc-c1YhzqFrUGJhw+jMZEXXTcT2xyDLnw-JQuVaQ@mail.gmail.com \
--to=geert@linux-m68k.org \
--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 \
--cc=xjtuwjp@gmail.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).