From: Tejun Heo <htejun@gmail.com>
To: Matthew Wilcox <matthew@wil.cx>
Cc: Jeff Garzik <jeff@garzik.org>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] Asynchronous scan support for libata
Date: Sat, 08 Sep 2007 19:40:27 +0200 [thread overview]
Message-ID: <46E2DE8B.5040708@gmail.com> (raw)
In-Reply-To: <20070908171917.GC6809@parisc-linux.org>
Matthew Wilcox wrote:
> On Sat, Sep 08, 2007 at 05:10:27PM +0900, Tejun Heo wrote:
>> I think it's generally okay although it would need to spend quite some
>> time in -mm and we'll need to exclude several drivers which require
>> host-wide silence for mode programming (the current code is buggy but
>> sequential probing hides it pretty well) till host-wide exclusion is
>> implemented.
>
> Can you tell me a bit more about these drivers? Would it be possible to
> convert them to one host/many channels, which would give us the exclusion
> we want?
IIRC, sata_promise is of this type and there probably are a few old PATA
ones. Ports on the host are mostly independent. There's no need for
cross-port synchronization for most of the time but configuring transfer
mode requires host-wide quiescence. Currently, the planned way to fix
the problem is to implement host-wide exclusion mechanism in the error
handler (summon EH of all other threads and wait till all of them are
parked) and it's on top of the TODO list, so I don't think it will take
too long.
Thanks.
--
tejun
next prev parent reply other threads:[~2007-09-08 17:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-06 21:05 [PATCH] Asynchronous scan support for libata Matthew Wilcox
2007-09-08 8:10 ` Tejun Heo
2007-09-08 17:19 ` Matthew Wilcox
2007-09-08 17:34 ` Jeff Garzik
2007-09-08 20:27 ` Tejun Heo
2007-09-08 17:40 ` Tejun Heo [this message]
2007-09-08 18:48 ` Alan Cox
2007-10-02 14:41 ` Jeff Garzik
2007-10-04 13:21 ` Matthew Wilcox
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=46E2DE8B.5040708@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=matthew@wil.cx \
/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).