From: Tejun Heo <htejun@gmail.com>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: jeff@garzik.org, linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.19 2/3] sata_promise: new EH conversion
Date: Wed, 06 Dec 2006 18:40:59 +0900 [thread overview]
Message-ID: <4576902B.3070006@gmail.com> (raw)
In-Reply-To: <200612060852.kB68q4i0024622@harpo.it.uu.se>
Mikael Pettersson wrote:
>> 3. we don't have them in ahci nor sata_sil24.
>
> But you do in sata_sil.c:sil_freeze().
Two versus one. It's democracy. :-)
>> But, having those flushes won't hurt either.
>
> libata doesn't specify in its documentation that these driver
> operations may have delayed behaviour, so I have to assume that
> side-effects are to be completed when the operations return.
> In fact, the documentation for __ata_port_freeze explicitly
> requires the port to not perform any operations until thawed.
> If I didn't flush, the port could do just that.
I can't fully understand the above paragraph. Please elaborate.
> Since the flushes clearly are safe I'd prefer to keep them, but
> of course I'll remove them if you or Jeff can guarantee that not
> flushing the PCI writes is OK.
I don't really know. AFAICT, things should work without those flushes.
ATA devices are often crappy and drivers are built to deal with those
kinds of spurious interrupts while frozen. And, yes, having it never
hurts. I'm just not quite sure what they guarantee. IRQ signals are
asynchronous to IOs, so flushing IO doesn't guarantee immediate IRQ
quiescence.
If you leave those flushes, that makes it two versus two. Universe will
be in balance. :-)
--
tejun
next prev parent reply other threads:[~2006-12-06 9:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 8:52 [PATCH 2.6.19 2/3] sata_promise: new EH conversion Mikael Pettersson
2006-12-06 9:40 ` Tejun Heo [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-12-06 8:53 Mikael Pettersson
2006-12-06 9:13 ` Jeff Garzik
2006-12-06 9:19 ` Tejun Heo
2006-12-01 9:58 Mikael Pettersson
2006-12-03 13:00 ` Tejun Heo
2006-12-03 13:03 ` Jeff Garzik
2006-12-03 13:19 ` Tejun Heo
2006-12-03 14:16 ` Arjan van de Ven
2006-12-06 9:38 ` Tejun Heo
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=4576902B.3070006@gmail.com \
--to=htejun@gmail.com \
--cc=jeff@garzik.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@it.uu.se \
/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).