From: Christoph Hellwig <hch@infradead.org>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org,
xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] xfs: honor the O_SYNC flag for aysnchronous direct I/O requests
Date: Sat, 28 Jan 2012 09:59:33 -0500 [thread overview]
Message-ID: <20120128145933.GA10931@infradead.org> (raw)
In-Reply-To: <1327698949-12616-2-git-send-email-jmoyer@redhat.com>
This looks pretty good. Did this past xfstests? I'd also like to add
tests actually executing this code path just, to be sure. E.g. variants
of aio-stress actually using O_SYNC. We can't easily test data really
made it to disk that way, although at least we make sure the code
doesn't break.
On Fri, Jan 27, 2012 at 04:15:47PM -0500, Jeff Moyer wrote:
> Hi,
>
> If a file is opened with O_SYNC|O_DIRECT, the drive cache does not get
> flushed after the write completion. Instead, it's flushed *before* the
> I/O is sent to the disk (in __generic_file_aio_write).
XFS doesn't actually use __generic_file_aio_write, so this sentence
isn't correct for XFS.
> + } else if (xfs_ioend_needs_cache_flush(ioend)) {
> + struct xfs_inode *ip = XFS_I(ioend->io_inode);
> + struct xfs_mount *mp = ip->i_mount;
> + int err;
> + int log_flushed = 0;
> +
> + /*
> + * Check to see if we only need to sync data. If so,
> + * we can skip the log flush.
> + */
> + if (IS_SYNC(ioend->io_inode) ||
> + (ioend->io_iocb->ki_filp->f_flags & __O_SYNC)) {
> + err = _xfs_log_force(mp, XFS_LOG_SYNC, &log_flushed);
Can you add a TODO comment that this actually is synchronous and thus
will block the I/O completion work queue?
Also you can use _xfs_log_force_lsn here as don't need to flush the
whole log, just up to the last lsn that touched the inode. Copy, or
better factor the code from xfs_dir_fsync for that.
Last but not least this won't catch timestamp updates. Given that I'm
about to send a series making timestamp updates transaction I would not
recommend you to bother with that, but if you want to take a look
at how xfs_file_fsync deals with them. Given that this series touches
the same area I'd also like to take your xfs patch in through the xfs tree
to avoid conflicts.
> @@ -47,6 +47,7 @@ STATIC int xfsbufd(void *);
> static struct workqueue_struct *xfslogd_workqueue;
> struct workqueue_struct *xfsdatad_workqueue;
> struct workqueue_struct *xfsconvertd_workqueue;
> +struct workqueue_struct *xfsflushd_workqueue;
>
> #ifdef XFS_BUF_LOCK_TRACKING
> # define XB_SET_OWNER(bp) ((bp)->b_last_holder = current->pid)
> @@ -1802,8 +1803,15 @@ xfs_buf_init(void)
> if (!xfsconvertd_workqueue)
> goto out_destroy_xfsdatad_workqueue;
>
> + xfsflushd_workqueue = alloc_workqueue("xfsflushd",
> + WQ_MEM_RECLAIM, 1);
This should allow a higher concurrently level, it's probably a good
idea to pass 0 and use the default.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-01-28 14:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-27 21:15 [patch|rfc][0/3] fix aio+dio+O_SYNC writes Jeff Moyer
2012-01-27 21:15 ` [PATCH 1/3] xfs: honor the O_SYNC flag for aysnchronous direct I/O requests Jeff Moyer
2012-01-28 14:59 ` Christoph Hellwig [this message]
2012-01-27 21:15 ` [PATCH 2/3] ext4: " Jeff Moyer
2012-02-02 17:31 ` Jan Kara
2012-02-06 16:20 ` Jeff Moyer
2012-02-06 16:58 ` Jan Kara
2012-02-08 15:11 ` Jeff Moyer
2012-02-13 18:27 ` Jan Kara
2012-01-27 21:15 ` [PATCH 3/3] filemap: don't call generic_write_sync for -EIOCBQUEUED Jeff Moyer
2012-01-28 15:08 ` Martin Steigerwald
2012-02-02 17:52 ` Jan Kara
2012-02-06 16:33 ` Jeff Moyer
2012-02-06 19:55 ` Christoph Hellwig
2012-02-07 20:39 ` Jeff Moyer
2012-02-08 16:09 ` Jan Kara
2012-02-08 16:38 ` Jeff Moyer
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=20120128145933.GA10931@infradead.org \
--to=hch@infradead.org \
--cc=jmoyer@redhat.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--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).