From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 3/3] XFS: Sort delayed write buffers before dispatch
Date: Mon, 4 Jan 2010 10:43:31 -0500 [thread overview]
Message-ID: <20100104154331.GA7924@infradead.org> (raw)
In-Reply-To: <1262401416-19546-4-git-send-email-david@fromorbit.com>
On Sat, Jan 02, 2010 at 02:03:36PM +1100, Dave Chinner wrote:
> Ideally this should use a list sort rather than requiring an
> external buffer to sort the buffers in, but for simplicity
> just do it via sort function. Followup patches are needed to
> take the list sort functions from the DRM and UBIFS code and
> make it a common function and to utilise it. That will allow
> sorting the entire delwri queue to be written in one go.
Maybe getting the common list sort in ASAP might be a good idea. That
way we could have it ready by the time this patchset is merged. If not
adding a new list sort to XFS temporarily might be a better idea than
artifically flattening the list.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-01-04 15:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-02 3:03 [RFC, PATCH 0/3] Kill async inode writeback Dave Chinner
2010-01-02 3:03 ` [PATCH 1/3] XFS: Use delayed write for inodes rather than async Dave Chinner
2010-01-02 3:03 ` [PATCH 2/3] XFS: Don't issue buffer IO direct from AIL push Dave Chinner
2010-01-02 3:03 ` [PATCH 3/3] XFS: Sort delayed write buffers before dispatch Dave Chinner
2010-01-02 13:08 ` Andi Kleen
2010-01-02 14:14 ` Dave Chinner
2010-01-04 15:43 ` Christoph Hellwig [this message]
2010-01-04 23:53 ` Dave Chinner
-- strict thread matches above, loose matches on Subject: below --
2010-01-05 0:04 [PATCH 0/3] Kill async inode writeback V2 Dave Chinner
2010-01-05 0:04 ` [PATCH 3/3] xfs: Sort delayed write buffers before dispatch Dave Chinner
2010-01-08 11:11 ` Christoph Hellwig
2010-01-08 11:17 ` Dave Chinner
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=20100104154331.GA7924@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.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