From: Jeff Garzik <jgarzik@pobox.com>
To: Doug Maxey <dwm@maxeymade.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Albert Lee <albertcc@tw.ibm.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>,
Bartlomiej Zolnierkiewicz <B.Zolnierkiewicz@elka.pw.edu.pl>,
Tejun Heo <htejun@gmail.com>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Subject: Re: Organized summary of the pacthes
Date: Sat, 9 Jul 2005 23:44:44 -0400 [thread overview]
Message-ID: <20050710034444.GD13883@havoc.gtf.org> (raw)
In-Reply-To: <200507100054.j6A0s6Ct025796@falcon30.maxeymade.com>
On Sat, Jul 09, 2005 at 07:54:06PM -0500, Doug Maxey wrote:
> >> However, I am pondering scrapping all the polling code, since on SATA,
> >> interrupt-driven mode is much more desirable.
> >
> >You need both interrupt and polled command issue. ACPI needs to be able
> >to issue taskfiles to the IDE drive fairly early during resume. Right
> >now this isn't done at all. If polled is there it might also prove a
> >useful way to reissue a command when you think the IRQ routing is hosed
> >8)
>
> This would be an enhancement, rather than something required currently,
> correct?
Switching over to interrupt-driven for SATA is basically a requirement.
Since the polling code is what exists now, it MAY be easier to leave it
in, which puts "leave in polling code" in the enhancement category.
Jeff
next prev parent reply other threads:[~2005-07-10 3:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <42C12A10.8030308@tw.ibm.com>
2005-06-28 15:21 ` Organized summary of the pacthes Jeff Garzik
2005-06-28 18:00 ` Alan Cox
2005-07-10 0:54 ` Doug Maxey
2005-07-10 3:44 ` Jeff Garzik [this message]
2005-06-30 8:43 ` Albert Lee
2005-06-30 12:45 ` Al Boldi
2005-07-02 5:24 ` Tejun Heo
2005-06-30 17:10 ` Olaf Hering
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=20050710034444.GD13883@havoc.gtf.org \
--to=jgarzik@pobox.com \
--cc=B.Zolnierkiewicz@elka.pw.edu.pl \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=albertcc@tw.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=dwm@maxeymade.com \
--cc=htejun@gmail.com \
--cc=linux-ide@vger.kernel.org \
/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).