From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jeff Garzik <jeff@garzik.org>
Cc: linux-ide@vger.kernel.org
Subject: Re: [PATCH] Re: libata: PIO bounce copies to avoid long IRQ off runs
Date: Tue, 29 Apr 2008 23:01:05 +0100 [thread overview]
Message-ID: <20080429230105.710cd464@core> (raw)
In-Reply-To: <20080429220128.GA25818@havoc.gtf.org>
On Tue, 29 Apr 2008 18:01:28 -0400
Jeff Garzik <jeff@garzik.org> wrote:
> I would tend to prefer this version...
>
> - allocate buffer at init time
> - use lesser-used KM_IRQ1
Seems reasonable enough. You actually want to deal with the buffer at run
time however because you care about two cases
1. Box with no highmem - easy to do compile time
2. Box with no high pages allocated - kind of hairy with gcc as
the crystal ball feature doesn't work.
prev parent reply other threads:[~2008-04-29 22:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 13:47 [PATCH] libata: PIO bounce copies to avoid long IRQ off runs Alan Cox
2008-04-29 15:51 ` Grant Grundler
2008-04-29 16:21 ` Alan Cox
2008-04-29 22:01 ` [PATCH] " Jeff Garzik
2008-04-29 22:01 ` Alan Cox [this message]
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=20080429230105.710cd464@core \
--to=alan@lxorguk.ukuu.org.uk \
--cc=jeff@garzik.org \
--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).