From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: mroos@linux.ee, linux-scsi@vger.kernel.org,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
linux-kernel@vger.kernel.org,
Arjan van de Ven <arjan@linux.intel.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH 1/4] async: introduce 'async_domain' type
Date: Fri, 25 May 2012 08:51:07 +0100 [thread overview]
Message-ID: <1337932267.2932.7.camel@dabdike.int.hansenpartnership.com> (raw)
In-Reply-To: <20120525075027.21933.75815.stgit@dwillia2-linux.jf.intel.com>
On Fri, 2012-05-25 at 00:50 -0700, Dan Williams wrote:
> This is in preparation for teaching async_synchronize_full() to sync all
> pending async work, and not just on the async_running domain. This
> conversion is functionally equivalent, just embedding the existing list
> in a new async_domain type.
This looks good, but I want Arjan and others who invented the async code
to speed up boot to comment on all of this. What was the intention of
async_synchronize_full() and if it wasn't to synchronise all domains,
should we fix the documentation and add a new primitive to do that,
since boot clearly assumes the all domains behaviour.
In the mean time, this is probably all a bit much for a merge window, so
I'll revert
commit a7a20d103994fd760766e6c9d494daa569cbfe06
Author: Dan Williams <dan.j.williams@intel.com>
Date: Thu Mar 22 17:05:11 2012 -0700
[SCSI] sd: limit the scope of the async probe domain
And we'll put whatever is chosen in early for the next merge window.
James
next prev parent reply other threads:[~2012-05-25 7:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-25 7:50 [RFT PATCH 0/4] fix / cleanup async scsi scanning Dan Williams
2012-05-25 7:50 ` [PATCH 1/4] async: introduce 'async_domain' type Dan Williams
2012-05-25 7:51 ` James Bottomley [this message]
2012-05-25 8:18 ` Dan Williams
2012-05-25 8:48 ` James Bottomley
2012-05-25 19:23 ` Rafael J. Wysocki
2012-05-25 13:31 ` Arjan van de Ven
2012-05-25 13:40 ` mroos
2012-05-25 15:05 ` Dan Williams
2012-05-27 22:34 ` Mark Brown
2012-05-25 7:50 ` [PATCH 2/4] async: make async_synchronize_full() flush all work regardless of domain Dan Williams
2012-05-25 7:50 ` [PATCH 3/4] scsi: queue async scan work to an async_schedule domain Dan Williams
2012-05-25 7:50 ` [PATCH 4/4] scsi: cleanup usages of scsi_complete_async_scans 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=1337932267.2932.7.camel@dabdike.int.hansenpartnership.com \
--to=james.bottomley@hansenpartnership.com \
--cc=arjan@linux.intel.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=lrg@ti.com \
--cc=mroos@linux.ee \
/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
all inboxes | Powered by JetHome®