From: Jan Kara <jack@suse.cz>
To: Christoph Hellwig <hch@lst.de>
Cc: Al Viro <viro@zeniv.linux.org.uk>, Nick Piggin <npiggin@suse.de>,
Jan Kara <jack@suse.cz>,
linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH] direct I/O fallback sync simplification
Date: Tue, 29 Sep 2009 15:08:00 +0200 [thread overview]
Message-ID: <20090929130800.GA11573@duck.suse.cz> (raw)
In-Reply-To: <20090923130730.GC10759@lst.de>
On Wed 23-09-09 15:07:30, Christoph Hellwig wrote:
> In the case of direct I/O falling back to buffered I/O we sync data
> twice currently: once at the end of generic_file_buffered_write using
> filemap_write_and_wait_range and once a little later in
> __generic_file_aio_write using do_sync_mapping_range with all flags set.
>
> The wait before write of the do_sync_mapping_range call does not make
> any sense, so just keep the filemap_write_and_wait_range call and move
> it to the right spot.
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Looks much better. Acked-by: Jan Kara <jack@suse.cz>
Honza
>
> Index: vfs-2.6.git/mm/filemap.c
> ===================================================================
> --- vfs-2.6.git.orig/mm/filemap.c 2009-09-22 14:20:59.917761567 -0300
> +++ vfs-2.6.git/mm/filemap.c 2009-09-22 14:28:01.833832530 -0300
> @@ -2265,15 +2265,6 @@ generic_file_buffered_write(struct kiocb
> *ppos = pos + status;
> }
>
> - /*
> - * If we get here for O_DIRECT writes then we must have fallen through
> - * to buffered writes (block instantiation inside i_size). So we sync
> - * the file data here, to try to honour O_DIRECT expectations.
> - */
> - if (unlikely(file->f_flags & O_DIRECT) && written)
> - status = filemap_write_and_wait_range(mapping,
> - pos, pos + written - 1);
> -
> return written ? written : status;
> }
> EXPORT_SYMBOL(generic_file_buffered_write);
> @@ -2372,10 +2363,7 @@ ssize_t __generic_file_aio_write(struct
> * semantics.
> */
> endbyte = pos + written_buffered - written - 1;
> - err = do_sync_mapping_range(file->f_mapping, pos, endbyte,
> - SYNC_FILE_RANGE_WAIT_BEFORE|
> - SYNC_FILE_RANGE_WRITE|
> - SYNC_FILE_RANGE_WAIT_AFTER);
> + err = filemap_write_and_wait_range(file->f_mapping, pos, endbyte);
> if (err == 0) {
> written = written_buffered;
> invalidate_mapping_pages(mapping,
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
prev parent reply other threads:[~2009-09-29 13:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-23 13:07 [PATCH] direct I/O fallback sync simplification Christoph Hellwig
2009-09-23 14:04 ` Jamie Lokier
2009-09-26 15:08 ` Christoph Hellwig
2009-09-29 21:30 ` Jamie Lokier
2009-09-30 12:05 ` Christoph Hellwig
2009-09-30 18:13 ` Jamie Lokier
2009-09-26 19:37 ` Nick Piggin
2009-09-29 13:08 ` Jan Kara [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=20090929130800.GA11573@duck.suse.cz \
--to=jack@suse.cz \
--cc=hch@lst.de \
--cc=linux-fsdevel@vger.kernel.org \
--cc=npiggin@suse.de \
--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).