[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100608084718.GB7869@dastard>
Date: Tue, 8 Jun 2010 18:47:18 +1000
From: Dave Chinner <david@...morbit.com>
To: Christof Schmitt <christof.schmitt@...ibm.com>
Cc: "Martin K. Petersen" <martin.petersen@...cle.com>,
Boaz Harrosh <bharrosh@...asas.com>,
linux-scsi@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Re: Wrong DIF guard tag on ext2 write
On Tue, Jun 08, 2010 at 09:15:35AM +0200, Christof Schmitt wrote:
> On Mon, Jun 07, 2010 at 01:40:21PM -0400, Martin K. Petersen wrote:
> > >>>>> "Boaz" == Boaz Harrosh <bharrosh@...asas.com> writes:
> >
> > Boaz> Do you remember some performance numbers that show degradation /
> > Boaz> sameness?
> >
> > Boaz> What type of work loads?
> >
> > I haven't been using XFS much for over a year. I'm using an internal
> > async I/O tool and btrfs for most of my DIX/DIF testing these days.
> >
> > But my original changes were along the lines of what Jan mentioned
> > earlier (hooking into page_mkwrite and waiting for writeback. I could
> > have sworn that I only did it for ext[23] and that XFS waited out of the
> > box but git proves me wrong). Anyway, I'll try to get some benchmarking
> > happening later this week.
>
> Is there a patch with this change available somewhere? It might be
> useful to patch a kernel with this XFS change for reliable DIF/DIX
> testing.
Adding a wait_on_page_writeback() call to page_mkwrite() won't help
by itself - you need to unmap the pages after transitioning them
from dirty to writeback but before the hardware starts processing
the IO if you want to lock out mmap writes this way....
Cheers,
Dave.
--
Dave Chinner
david@...morbit.com
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists