linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: james <jamessteward@optusnet.com.au>
To: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
Cc: Russell King <rmk@arm.linux.org.uk>, Tejun Heo <htejun@gmail.com>,
	"linux-ide@vger.kernel.org" <linux-ide@vger.kernel.org>
Subject: Re: [PATCH] ide: add dcache flushing after PIO
Date: Sun, 08 Jan 2006 11:50:24 +1100	[thread overview]
Message-ID: <1136681424.15944.12.camel@localhost.localdomain> (raw)
In-Reply-To: <58cb370e0601071441v2d2e8f6eq18ebd8ea0280d1d1@mail.gmail.com>

On Sat, 2006-01-07 at 23:41 +0100, Bartlomiej Zolnierkiewicz wrote:
> On 1/7/06, Russell King <rmk@arm.linux.org.uk> wrote:
> > 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.
> 
> Tejun posted RFC to lkml which got zero replies so I thought
> that I will apply his patch if it *works*.
> 
> We can fix the problem in IDE locally - fine with me - but I want
> to know if we are actually *really* fixing the problem or just adding
> more confusion to IDE subsystem.
> 
> > > 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.
> 
> OK, we have discussed the way to fix the problem.
> 
> Still nothing was said whether this patch *actually* works or not.
> 
> > > 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?
> 
> Test original Tejun's patch then.
> 
> I need some help from you and other ARM folks to fix this properly,
> I'm just a stupid IDE developer... :-)

I'm happy to see if it works.  I'm running 2.6.13.2 so if it applies
cleanly...

Any hints on what to look for?

I have the cachepolicy=writethrough kernel arg set at the mo to work
around the problem - I'll not set that see if I can run apps from the CF
I guess.

I saw segvs w/o the cachepolicy=... set.  So is there anything else I
need to do?  What other tests can I do and feedback can I give?

Please advise.

Russell, I note the comments by you and others above on Tejun's patch,
is there anything you (or others) think I should look for in testing
this?


BTW - thanks for keeping this going.

Happy New Year and warm regards,
James.

43 degrees C in Melbourne, Australia New Years Eve!

> 
> Bartlomiej
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ide" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2006-01-08  0:41 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
2006-01-07 22:41                       ` Bartlomiej Zolnierkiewicz
2006-01-08  0:50                         ` james [this message]
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=1136681424.15944.12.camel@localhost.localdomain \
    --to=jamessteward@optusnet.com.au \
    --cc=bzolnier@gmail.com \
    --cc=htejun@gmail.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=rmk@arm.linux.org.uk \
    /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).