From: Ben Myers <bpm@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Martin Boutin <martboutin@gmail.com>,
"Kernel.org-Linux-RAID" <linux-raid@vger.kernel.org>,
Eric Sandeen <sandeen@redhat.com>, xfs-oss <xfs@oss.sgi.com>,
Christoph Hellwig <hch@infradead.org>,
"Kernel.org-Linux-EXT4" <linux-ext4@vger.kernel.org>
Subject: Re: Filesystem writes on RAID5 too slow
Date: Wed, 11 Dec 2013 13:09:45 -0600 [thread overview]
Message-ID: <20131211190945.GF1935@sgi.com> (raw)
In-Reply-To: <20131211002753.GD10988@dastard>
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@redhat.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
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2013-12-11 19:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-18 16:02 Filesystem writes on RAID5 too slow Martin Boutin
2013-11-18 18:28 ` Eric Sandeen
2013-11-19 0:57 ` Dave Chinner
2013-11-21 9:11 ` Martin Boutin
2013-11-21 9:26 ` Dave Chinner
2013-11-21 9:50 ` Martin Boutin
2013-11-21 13:31 ` Martin Boutin
2013-11-21 16:35 ` Martin Boutin
2013-11-21 23:41 ` Dave Chinner
2013-11-22 9:21 ` Christoph Hellwig
2013-11-22 22:40 ` Dave Chinner
2013-11-23 8:41 ` Christoph Hellwig
2013-11-24 23:21 ` Dave Chinner
2013-11-22 13:33 ` Martin Boutin
2013-12-10 19:18 ` Christoph Hellwig
2013-12-11 0:27 ` Dave Chinner
2013-12-11 19:09 ` Ben Myers [this message]
2013-11-18 18:41 ` Roman Mamedov
2013-11-18 19:25 ` Roman Mamedov
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=20131211190945.GF1935@sgi.com \
--to=bpm@sgi.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=martboutin@gmail.com \
--cc=sandeen@redhat.com \
--cc=xfs@oss.sgi.com \
/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).