From: Lachlan McIlroy <lachlan@sgi.com>
To: David Chinner <dgc@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: [patch] Use BIO_META tags for metadata rather than BIO_SYNC
Date: Tue, 22 Jan 2008 14:50:48 +1100 [thread overview]
Message-ID: <47956818.1010808@sgi.com> (raw)
In-Reply-To: <20080121041826.GB155259@sgi.com>
Looks good.
David Chinner wrote:
> Improve metadata I/O merging in the elevator
>
> Change all async metadata buffers to use [READ|WRITE]_META I/O types
> so that the I/O doesn't get issued immediately. This allows merging
> of adjacent metadata requests but still prioritises them over bulk
> data. This shows a 10-15% improvement in sequential create speed of
> small files.
>
> Don't include the log buffers in this classification - leave them
> as sync types so they are issued immediately.
>
> Signed-off-by: Dave Chinner <dgc@sgi.com>
> ---
> fs/xfs/linux-2.6/xfs_buf.c | 6 +++++-
> include/linux/fs.h | 1 +
> 2 files changed, 6 insertions(+), 1 deletion(-)
>
> Index: 2.6.x-xfs-new/fs/xfs/linux-2.6/xfs_buf.c
> ===================================================================
> --- 2.6.x-xfs-new.orig/fs/xfs/linux-2.6/xfs_buf.c 2007-12-19 11:56:47.977477993 +1100
> +++ 2.6.x-xfs-new/fs/xfs/linux-2.6/xfs_buf.c 2007-12-19 11:56:52.200932303 +1100
> @@ -1136,10 +1136,14 @@ _xfs_buf_ioapply(
> if (bp->b_flags & XBF_ORDERED) {
> ASSERT(!(bp->b_flags & XBF_READ));
> rw = WRITE_BARRIER;
> - } else if (bp->b_flags & _XBF_RUN_QUEUES) {
> + } else if (bp->b_flags & XBF_LOG_BUFFER) {
> ASSERT(!(bp->b_flags & XBF_READ_AHEAD));
> bp->b_flags &= ~_XBF_RUN_QUEUES;
> rw = (bp->b_flags & XBF_WRITE) ? WRITE_SYNC : READ_SYNC;
> + } else if (bp->b_flags & _XBF_RUN_QUEUES) {
> + ASSERT(!(bp->b_flags & XBF_READ_AHEAD));
> + bp->b_flags &= ~_XBF_RUN_QUEUES;
> + rw = (bp->b_flags & XBF_WRITE) ? WRITE_META : READ_META;
> } else {
> rw = (bp->b_flags & XBF_WRITE) ? WRITE :
> (bp->b_flags & XBF_READ_AHEAD) ? READA : READ;
> Index: 2.6.x-xfs-new/include/linux/fs.h
> ===================================================================
> --- 2.6.x-xfs-new.orig/include/linux/fs.h 2007-12-19 01:11:16.495229881 +1100
> +++ 2.6.x-xfs-new/include/linux/fs.h 2007-12-19 11:56:52.352912667 +1100
> @@ -83,6 +83,7 @@ extern int dir_notify_enable;
> #define READ_SYNC (READ | (1 << BIO_RW_SYNC))
> #define READ_META (READ | (1 << BIO_RW_META))
> #define WRITE_SYNC (WRITE | (1 << BIO_RW_SYNC))
> +#define WRITE_META (WRITE | (1 << BIO_RW_META))
> #define WRITE_BARRIER ((1 << BIO_RW) | (1 << BIO_RW_BARRIER))
>
> #define SEL_IN 1
>
>
>
next prev parent reply other threads:[~2008-01-22 3:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 4:18 [patch] Use BIO_META tags for metadata rather than BIO_SYNC David Chinner
2008-01-22 3:50 ` Lachlan McIlroy [this message]
2008-07-23 3:49 ` Eric Sandeen
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=47956818.1010808@sgi.com \
--to=lachlan@sgi.com \
--cc=dgc@sgi.com \
--cc=xfs-dev@sgi.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