From: Jeff Moyer <jmoyer@redhat.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, linux-btrfs@vger.kernel.org,
ocfs2-devel@oss.oracle.com, xfs@oss.sgi.com,
Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, cluster-devel@redhat.com,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/4] Generic O_SYNC AIO DIO handling
Date: Fri, 10 Feb 2012 11:09:09 -0500 [thread overview]
Message-ID: <x49aa4qpt5m.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <1328889842-23231-1-git-send-email-jack@suse.cz> (Jan Kara's message of "Fri, 10 Feb 2012 17:03:58 +0100")
Jan Kara <jack@suse.cz> writes:
> Hi Jeff,
>
> these patches implement generic way of handling O_SYNC AIO DIO. They work
> for all filesystems except for ext4 and xfs. Thus together with your patches,
> all filesystems should handle O_SYNC AIO DIO correctly. I've tested ext3,
> btrfs, and xfs (to check that I didn't break anything when the generic code
> is unused) and things seem to work fine. Will you add these patches to your
> series please? Thanks.
Thanks, Jan! I'll add them in and give them some testing. I should be
ready to repost the series early next week.
Cheers,
Jeff
prev parent reply other threads:[~2012-02-10 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 16:03 [PATCH 0/4] Generic O_SYNC AIO DIO handling Jan Kara
2012-02-10 16:03 ` [PATCH 1/4] vfs: Handle O_SYNC AIO DIO in generic code properly Jan Kara
2012-02-10 16:04 ` [PATCH 2/4] ocfs2: Use generic handlers of O_SYNC AIO DIO Jan Kara
2012-02-10 16:04 ` [PATCH 3/4] gfs2: " Jan Kara
2012-02-13 9:42 ` [Cluster-devel] " Steven Whitehouse
2012-02-10 16:04 ` [PATCH 4/4] btrfs: " Jan Kara
2012-02-10 16:09 ` Jeff Moyer [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=x49aa4qpt5m.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=cluster-devel@redhat.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ocfs2-devel@oss.oracle.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).