From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Alan Stern <stern@rowland.harvard.edu>, Tejun Heo <tj@kernel.org>,
Len Brown <len.brown@intel.com>,
linux-scsi <linux-scsi@vger.kernel.org>,
Phillip Susi <psusi@ubuntu.com>,
IDE/ATA development list <linux-ide@vger.kernel.org>,
Todd Brandt <todd.e.brandt@linux.intel.com>
Subject: Re: [PATCH v5 3/3] scsi: async sd resume
Date: Sat, 15 Mar 2014 14:47:52 -0700 [thread overview]
Message-ID: <1394920072.2166.29.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <CAPcyv4iVMss=Vj8O9RR2GGCw-4uesw1MKj-qFuaXZqtTz1Cqdg@mail.gmail.com>
On Fri, 2014-03-14 at 13:11 -0700, Dan Williams wrote:
> On Mon, Mar 10, 2014 at 11:29 PM, James Bottomley
> <James.Bottomley@hansenpartnership.com> wrote:
> >> > In the long game, though this whole debate is moot: setups with hard
> >> > wired start times adhere to them regardless of what the system does, so
> >> > they ignore start unit commands. Systems without hard wired start times
> >> > can usually be started at once, so us introducing a delay is unnecessary
> >> > in either case.
> >>
> >> Ok, then I'll let the patch stand as is.
> >
> > Sounds good.
> >
> > James
> >
> >
>
> Well, one more chirp about this. If the user has disabled async
> scanning by CONFIG_SCSI_SCAN_ASYNC=n or scsi_mod.scan != "async" then
> resume should follow suit. I'll include this in the next rev.
Hm, OK, if this is tied at the hip to async scanning, why do you need
another async domain for it? Why not just use the current async
scanning domain ... it will actually probably resolve a few nasty (but
wholly manufactured) races where scanning races with suspend.
James
next prev parent reply other threads:[~2014-03-15 21:47 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-05 20:17 [PATCH v5 0/3] Accelerate Storage Resume (2x or more) Dan Williams
2014-03-05 20:17 ` [PATCH v5 1/3] libata, libsas: kill pm_result and related cleanup Dan Williams
2014-03-10 20:29 ` Tejun Heo
2014-03-10 20:44 ` Tejun Heo
2014-03-05 20:17 ` [PATCH v5 2/3] libata: async resume Dan Williams
2014-12-19 23:46 ` Phillip Susi
2014-12-20 1:42 ` Phillip Susi
2014-03-05 20:17 ` [PATCH v5 3/3] scsi: async sd resume Dan Williams
2014-03-07 15:42 ` Alan Stern
2014-03-08 0:41 ` Dan Williams
2014-03-08 2:52 ` Dan Williams
2014-03-10 15:49 ` Alan Stern
2014-03-10 20:43 ` Tejun Heo
2014-03-10 20:56 ` Dan Williams
2014-03-10 20:59 ` Alan Stern
2014-03-10 21:06 ` Dan Williams
2014-03-10 22:41 ` Phillip Susi
2014-03-11 4:19 ` James Bottomley
2014-03-11 4:47 ` Dan Williams
2014-03-11 5:16 ` James Bottomley
2014-03-11 5:26 ` Dan Williams
2014-03-11 6:29 ` James Bottomley
2014-03-14 20:11 ` Dan Williams
2014-03-15 21:47 ` James Bottomley [this message]
2014-03-15 23:35 ` Dan Williams
2014-03-16 18:21 ` James Bottomley
2014-03-17 18:20 ` Dan Williams
2014-03-21 0:09 ` Dan Williams
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=1394920072.2166.29.camel@dabdike.int.hansenpartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=dan.j.williams@intel.com \
--cc=len.brown@intel.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=psusi@ubuntu.com \
--cc=stern@rowland.harvard.edu \
--cc=tj@kernel.org \
--cc=todd.e.brandt@linux.intel.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