From: Jan Kara <jack@suse.cz>
To: linux-fsdevel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>,
linux-ext4@vger.kernel.org, Jan Kara <jack@suse.cz>,
Al Viro <viro@ZenIV.linux.org.uk>,
xfs@oss.sgi.com
Subject: [PATCH 0/2 v2] Fix O_SYNC AIO DIO
Date: Wed, 14 Aug 2013 11:10:54 +0200 [thread overview]
Message-ID: <1376471456-11966-1-git-send-email-jack@suse.cz> (raw)
Hello,
this is second iteration of patches to fix handling of O_SYNC AIO DIO.
Since previous version I've addressed Dave's comments:
- slightly expanded changelog of the first patch
- workqueue is now created with parameters allowing paralelism
- workqueue name contains sb->s_id
- workqueue is created on demand (I decided to do this to reduce the overhead
in unnecessary cases)
The patchset survives xfstests run for ext4 & xfs so it should be sane. Since
this touches several filesystems (although only ext4 & xfs are non-trivial),
the question is who should carry these patches. Maybe Al? But since xfs and
ext4 changes are non-trivial, I'd like to have a review from their
developers...
Honza
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
WARNING: multiple messages have this Message-ID (diff)
From: Jan Kara <jack@suse.cz>
To: linux-fsdevel@vger.kernel.org
Cc: linux-ext4@vger.kernel.org, xfs@oss.sgi.com,
Christoph Hellwig <hch@infradead.org>,
Al Viro <viro@ZenIV.linux.org.uk>, Jan Kara <jack@suse.cz>
Subject: [PATCH 0/2 v2] Fix O_SYNC AIO DIO
Date: Wed, 14 Aug 2013 11:10:54 +0200 [thread overview]
Message-ID: <1376471456-11966-1-git-send-email-jack@suse.cz> (raw)
Hello,
this is second iteration of patches to fix handling of O_SYNC AIO DIO.
Since previous version I've addressed Dave's comments:
- slightly expanded changelog of the first patch
- workqueue is now created with parameters allowing paralelism
- workqueue name contains sb->s_id
- workqueue is created on demand (I decided to do this to reduce the overhead
in unnecessary cases)
The patchset survives xfstests run for ext4 & xfs so it should be sane. Since
this touches several filesystems (although only ext4 & xfs are non-trivial),
the question is who should carry these patches. Maybe Al? But since xfs and
ext4 changes are non-trivial, I'd like to have a review from their
developers...
Honza
next reply other threads:[~2013-08-14 9:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 9:10 Jan Kara [this message]
2013-08-14 9:10 ` [PATCH 0/2 v2] Fix O_SYNC AIO DIO Jan Kara
2013-08-14 9:10 ` [PATCH 1/2] direct-io: Implement generic deferred AIO completions Jan Kara
2013-08-14 9:10 ` [PATCH 2/2] direct-io: Handle O_(D)SYNC AIO Jan Kara
2013-08-14 9:10 ` Jan Kara
2013-08-30 15:53 ` [PATCH 0/2 v2] Fix O_SYNC AIO DIO Al Viro
2013-08-30 15:53 ` Al Viro
2013-09-04 10:54 ` Jan Kara
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=1376471456-11966-1-git-send-email-jack@suse.cz \
--to=jack@suse.cz \
--cc=hch@infradead.org \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.