From: Christoph Hellwig <hch@lst.de>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>,
viro@zeniv.linux.org.uk, linux-fsdevel@vger.kernel.org,
Trond.Myklebust@netapp.com, dhowells@redhat.com
Subject: Re: [PATCH 1/2] make sure data is on disk before calling ->write_inode
Date: Thu, 14 Jan 2010 07:21:06 +0100 [thread overview]
Message-ID: <20100114062106.GA16739@lst.de> (raw)
In-Reply-To: <20100113162154.f7e7af49.akpm@linux-foundation.org>
On Wed, Jan 13, 2010 at 04:21:54PM -0800, Andrew Morton wrote:
> hm, yeah, it's hard to see how this reordering can harm throughput much.
>
> nfs_write_inode() has vanished in linux-enxt so I just dropped all the
> nfs parts of these two patches. You might want to check that.
That's because linux-next has an ugly workaround for the all calling
conventions. The nfs updates in -next should be dropped / reworked
instead.
prev parent reply other threads:[~2010-01-14 6:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-11 17:30 [PATCH 1/2] make sure data is on disk before calling ->write_inode Christoph Hellwig
2010-01-12 0:41 ` Dave Chinner
2010-01-14 0:21 ` Andrew Morton
2010-01-14 6:21 ` 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=20100114062106.GA16739@lst.de \
--to=hch@lst.de \
--cc=Trond.Myklebust@netapp.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).