From: Jeff Moyer <jmoyer@redhat.com>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
linux-fsdevel@vger.kernel.org, mpatocka@redhat.com
Subject: Re: [rfc][patch] mm: direct io less aggressive syncs and invalidates
Date: Tue, 28 Oct 2008 17:11:02 -0400 [thread overview]
Message-ID: <x4963nc2zo9.fsf@segfault.boston.devel.redhat.com> (raw)
In-Reply-To: <20081028155421.GC3082@wotan.suse.de> (Nick Piggin's message of "Tue, 28 Oct 2008 16:54:21 +0100")
Nick Piggin <npiggin@suse.de> writes:
> Direct IO can invalidate and sync a lot of pagecache pages in the mapping. A
> 4K direct IO will actually try to sync and/or invalidate the pagecache of the
> entire file, for example (which might be many GB or TB large).
>
> Improve this by doing range syncs. Also, memory no longer has to be unmapped
> to catch the dirty bits for syncing, as dirty bits would remain coherent due to
> dirty mmap accounting.
>
> This should fix the immediate DM deadlocks when doing direct IO reads to
> block device with a mounted filesystem, if only by papering over the problem
> somewhat rather than addressing the fsync starvation cases. Not that the
> patch itself is a hack, but for this particular problem it is not really
> the correct solution IMO. But anyway, this might be more appropriate to go
> into stable kernels if this DM deadlock is biting users.
>
> Yes, I still need to put more time into finishing my pagecache tag based
> sync solution. Sorry :(
>
>
> ---
> Index: linux-2.6/mm/filemap.c
> ===================================================================
> --- linux-2.6.orig/mm/filemap.c 2008-10-03 11:21:31.000000000 +1000
> +++ linux-2.6/mm/filemap.c 2008-10-03 12:00:17.000000000 +1000
> @@ -1304,11 +1304,8 @@ generic_file_aio_read(struct kiocb *iocb
> goto out; /* skip atime */
> size = i_size_read(inode);
> if (pos < size) {
> - retval = filemap_write_and_wait(mapping);
> - if (!retval) {
> - retval = mapping->a_ops->direct_IO(READ, iocb,
> + retval = mapping->a_ops->direct_IO(READ, iocb,
> iov, pos, nr_segs);
> - }
So why is it safe to get rid of this? Can't this result in reading
stale data from disk?
The rest looks good to me. I ran the aio-dio-regress tests against this
kernel on a UP machine, and they all passed. The kernel didn't boot on
my SMP box, though. Nick, any chance you could grab that test suite and
run it on an smp system?
http://git.kernel.org/?p=linux/kernel/git/zab/aio-dio-regress.git;a=summary
Thanks,
Jeff
next prev parent reply other threads:[~2008-10-28 21:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 15:54 [rfc][patch] mm: direct io less aggressive syncs and invalidates Nick Piggin
2008-10-28 21:11 ` Jeff Moyer [this message]
2008-10-28 23:52 ` Nick Piggin
2008-10-29 13:12 ` Jeff Moyer
2008-10-29 21:47 ` Dave Chinner
2008-10-30 2:11 ` Nick Piggin
2008-10-30 19:14 ` Jeff Moyer
2008-10-29 0:56 ` Jamie Lokier
2008-10-29 13:30 ` Jeff Moyer
2008-10-29 21:48 ` Dave Chinner
2008-10-29 14:02 ` Mikulas Patocka
2008-10-30 2:08 ` Nick Piggin
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=x4963nc2zo9.fsf@segfault.boston.devel.redhat.com \
--to=jmoyer@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=npiggin@suse.de \
/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).