From: Russell King <rmk@arm.linux.org.uk>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Tejun Heo <htejun@gmail.com>,
James Steward <james.steward@dynamicratings.com>,
"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] ide: add dcache flushing after PIO
Date: Sat, 7 Jan 2006 21:22:49 +0000 [thread overview]
Message-ID: <20060107212248.GJ31384@flint.arm.linux.org.uk> (raw)
In-Reply-To: <58cb370e0601071217x390fc1fpbbc9866b38ac28d7@mail.gmail.com>
On Sat, Jan 07, 2006 at 09:17:11PM +0100, Bartlomiej Zolnierkiewicz wrote:
> On 1/7/06, Russell King <rmk@arm.linux.org.uk> wrote:
> > On Wed, Dec 21, 2005 at 05:54:16PM +0000, Russell King wrote:
> > > DaveM vetoed that with good reason - the VM layer doesn't know whether
> > > the driver is doing PIO or not. If it is doing PIO, it needs the
> > > cache flush. If it's doing DMA, the cache flush is entirely a
> > > performance bottleneck.
> >
> > Bart,
> >
> > Did you miss my message, or have you decided to pay no further
> > attention to this issue?
>
> No, I'm waiting for ARM folks to give Tejun and me some feedback.
We have, and I think it's been soo long that you're now confused.
See the entire thread on marc:
http://marc.theaimsgroup.com/?t=113517374400003&r=1&w=2
Yes, Tejun produced a patch and I queried whether it was going to
far. There was a bit of discussion which resulted in a comment from
you saying:
| After reading excellent explanation by rmk I think that it should be
| fixed at VM layer (filemap_nopage() perhaps).
To which I replied:
| DaveM vetoed that with good reason - the VM layer doesn't know whether
| the driver is doing PIO or not. If it is doing PIO, it needs the
| cache flush. If it's doing DMA, the cache flush is entirely a
| performance bottleneck.
That's where we stand now - I'm waiting for some progress.
> So far there was none and nobody seemed to care to test/comment
> this patch ("works fine" is enough).
Odd, as demonstrated by the linux-ide archives above I've already
commented on it.
> What about testing the patch instead?
Since there hasn't been a follow-up patch, there isn't anything to
test. Please can we have a revised patch so folk _can_ do some
testing?
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2006-01-07 21:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 0:47 Execute from CF causes segmentation faults James Steward
2005-12-20 12:52 ` Tejun Heo
2005-12-20 16:23 ` Bartlomiej Zolnierkiewicz
2005-12-21 9:48 ` Tejun Heo
2005-12-21 14:00 ` [PATCH] ide: add dcache flushing after PIO Tejun Heo
2005-12-21 14:03 ` Russell King
2005-12-21 14:43 ` Tejun Heo
2005-12-21 15:57 ` Bartlomiej Zolnierkiewicz
2005-12-21 16:00 ` Tejun Heo
2005-12-21 17:54 ` Russell King
2006-01-07 17:06 ` Russell King
2006-01-07 20:17 ` Bartlomiej Zolnierkiewicz
2006-01-07 21:22 ` Russell King [this message]
2006-01-07 22:41 ` Bartlomiej Zolnierkiewicz
2006-01-08 0:50 ` james
2006-01-09 9:08 ` Russell King
2006-01-09 9:16 ` Tejun Heo
2005-12-21 15:01 ` Execute from CF causes segmentation faults Russell King
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=20060107212248.GJ31384@flint.arm.linux.org.uk \
--to=rmk@arm.linux.org.uk \
--cc=bzolnier@gmail.com \
--cc=htejun@gmail.com \
--cc=james.steward@dynamicratings.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).