From: Nick Piggin <npiggin@suse.de>
To: Andrew Morton <akpm@linux-foundation.org>, linux-fsdevel@vger.kernel.org
Cc: mpatocka@redhat.com
Subject: [rfc][patch] mm: direct io less aggressive syncs and invalidates
Date: Tue, 28 Oct 2008 16:54:21 +0100 [thread overview]
Message-ID: <20081028155421.GC3082@wotan.suse.de> (raw)
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);
- }
if (retval > 0)
*ppos = pos + retval;
if (retval) {
@@ -2110,18 +2107,10 @@ generic_file_direct_write(struct kiocb *
if (count != ocount)
*nr_segs = iov_shorten((struct iovec *)iov, *nr_segs, count);
- /*
- * Unmap all mmappings of the file up-front.
- *
- * This will cause any pte dirty bits to be propagated into the
- * pageframes for the subsequent filemap_write_and_wait().
- */
write_len = iov_length(iov, *nr_segs);
end = (pos + write_len - 1) >> PAGE_CACHE_SHIFT;
- if (mapping_mapped(mapping))
- unmap_mapping_range(mapping, pos, write_len, 0);
- written = filemap_write_and_wait(mapping);
+ written = filemap_write_and_wait_range(mapping, pos, pos + write_len - 1);
if (written)
goto out;
@@ -2507,7 +2496,8 @@ generic_file_buffered_write(struct kiocb
* the file data here, to try to honour O_DIRECT expectations.
*/
if (unlikely(file->f_flags & O_DIRECT) && written)
- status = filemap_write_and_wait(mapping);
+ status = filemap_write_and_wait_range(mapping,
+ pos, pos + written - 1);
return written ? written : status;
}
next reply other threads:[~2008-10-28 15:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-28 15:54 Nick Piggin [this message]
2008-10-28 21:11 ` [rfc][patch] mm: direct io less aggressive syncs and invalidates Jeff Moyer
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=20081028155421.GC3082@wotan.suse.de \
--to=npiggin@suse.de \
--cc=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=mpatocka@redhat.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).