[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20131211190945.GF1935@sgi.com>
Date: Wed, 11 Dec 2013 13:09:45 -0600
From: Ben Myers <bpm@....com>
To: Dave Chinner <david@...morbit.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Martin Boutin <martboutin@...il.com>,
"Kernel.org-Linux-RAID" <linux-raid@...r.kernel.org>,
xfs-oss <xfs@....sgi.com>,
"Kernel.org-Linux-EXT4" <linux-ext4@...r.kernel.org>,
Eric Sandeen <sandeen@...hat.com>
Subject: Re: Filesystem writes on RAID5 too slow
Hi,
On Wed, Dec 11, 2013 at 11:27:53AM +1100, Dave Chinner wrote:
> On Tue, Dec 10, 2013 at 11:18:03AM -0800, Christoph Hellwig wrote:
> > > xfs: align initial file allocations correctly.
> > >
> > > From: Dave Chinner <dchinner@...hat.com>
> > >
> > > The function xfs_bmap_isaeof() is used to indicate that an
> > > allocation is occurring at or past the end of file, and as such
> > > should be aligned to the underlying storage geometry if possible.
> > >
> > > Commit 27a3f8f ("xfs: introduce xfs_bmap_last_extent") changed the
> > > behaviour of this function for empty files - it turned off
> > > allocation alignment for this case accidentally. Hence large initial
> > > allocations from direct IO are not getting correctly aligned to the
> > > underlying geometry, and that is cause write performance to drop in
> > > alignment sensitive configurations.
> > >
> > > Fix it by considering allocation into empty files as requiring
> > > aligned allocation again.
> >
> > Seems like this one didn't get picked up yet?
>
> I'm about to resend all my outstanding patches...
Sorry I didn't see that one. If you stick the keyword 'patch' in the subject I
tend to do a bit better.
Regards,
Ben
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists