mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: "K. Y. Srinivasan" <kys@microsoft.com>
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
Date: Fri, 20 Sep 2013 13:32:22 -0700	[thread overview]
Message-ID: <20130920203222.GA14306@kroah.com> (raw)
In-Reply-To: <1379705547-15028-1-git-send-email-kys@microsoft.com>

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 send
> you a patch for this.

A module parameter don't make sense for a per-device value, does it?

greg k-h

  reply	other threads:[~2013-09-20 20:31 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-20 19:32 K. Y. Srinivasan
2013-09-20 20:32 ` Greg KH [this message]
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
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=20130920203222.GA14306@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=devel@linuxdriverproject.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=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

Powered by JetHome