From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: preallocation transactions do not need to be synchronous
Date: Thu, 17 Mar 2011 10:23:13 -0400 [thread overview]
Message-ID: <20110317142313.GA32673@infradead.org> (raw)
In-Reply-To: <20110310073634.GA25374@infradead.org>
On Thu, Mar 10, 2011 at 02:36:34AM -0500, Christoph Hellwig wrote:
> I had the same patch in my queue, but it turns out even that isn't
> enough for good performance when used fallocate in the fast path (e.g.
> recent Samba). I'll send a more comprehensive optimization that
> includes this soon.
>
> I also refactored the whole area to make the various flags more
> sensible.
Given that 2.6.38 is out now and I won't have my series ready in time
I'm fine with putting your minimal version in for now, I'll port mine
on top.
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2011-03-17 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 23:37 [PATCH] xfs: preallocation transactions do not need to be synchronous Dave Chinner
2011-03-10 7:36 ` Christoph Hellwig
2011-03-17 14:23 ` Christoph Hellwig [this message]
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=20110317142313.GA32673@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