From: Andrew Morton <akpm@osdl.org>
To: Jeff Moyer <jmoyer@redhat.com>
Cc: Zach Brown <zach.brown@oracle.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch] call truncate_inode_pages in the DIO fallback to buffered I/O path
Date: Wed, 4 Oct 2006 11:16:03 -0700 [thread overview]
Message-ID: <20061004111603.20cdaa35.akpm@osdl.org> (raw)
In-Reply-To: <x49mz8c6k83.fsf@segfault.boston.devel.redhat.com>
On Wed, 04 Oct 2006 13:53:32 -0400
Jeff Moyer <jmoyer@redhat.com> wrote:
> ==> Regarding Re: [patch] call truncate_inode_pages in the DIO fallback to buffered I/O path; Zach Brown <zach.brown@oracle.com> adds:
>
> >> Why is this a problem? It's just like someone did a write(), and we'll
> >> invalidate the pagecache on the next direct-io operation.
>
> zach.brown> This was noticed as a distro regression as they moved from the
> zach.brown> kernels that used to invalidate the entire address space on
> zach.brown> direct io ops to more modern ones that only invalidate the
> zach.brown> region being written.
>
> Right.
Change app to use sync_file_range() followed by
posix_fadvise(POSIX_FADV_DONTNEED). Problem solved.
We have lots of nice new tools in-kernel which permit applications to
manipulate and to invalidate pagecache. Please, start using them rather
than pushing bits of oracle into the core vfs ;)
> zach.brown> You can end up with significant memory pressure after this
> zach.brown> change with a large enough working set on disk.
>
> >> eek. truncate_inode_pages() will throw away dirty data. Very
> >> dangerous, much chin-scratching needed.
>
> zach.brown> Yeah, I failed to tell Jeff that it should be calling
> zach.brown> filemap_fdatawrite() first to get things into writeback. (And
> zach.brown> presumably not truncating if that returns an error.)
>
> Ahh, that explains it. The strange thing is that my test validates the
> file afterwards, and I was seeing correct data.
That is strange, because the truncate_inode_pages() will throw away the
dirty pagecache pages which the application just wrote to. Maybe the file
was opened O_SYNC or something.
> I'll repost after another round of testing.
Please, no truncate_inode_pages. For this application, the far-safer
invalidate_inode_pages() would suffice.
However no kernel change is needed.
And no sneaking changes like this into vendor kernels either! Fix Oracle.
next prev parent reply other threads:[~2006-10-04 18:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 17:04 [patch] call truncate_inode_pages in the DIO fallback to buffered I/O path Jeff Moyer
2006-10-04 17:25 ` Andrew Morton
2006-10-04 17:51 ` Zach Brown
2006-10-04 17:53 ` Jeff Moyer
2006-10-04 18:16 ` Andrew Morton [this message]
2006-10-04 18:40 ` Zach Brown
2006-10-04 19:16 ` Andrew Morton
2006-10-04 20:53 ` Jeff Moyer
2006-10-04 21:22 ` Jeff Moyer
2006-10-04 23:55 ` Andrew Morton
2006-10-05 19:31 ` Jeff Moyer
2006-10-06 20:11 ` Andrew Morton
2006-10-11 16:48 ` jmoyer
2006-10-11 18:37 ` Andrew Morton
2006-10-12 22:01 ` Jeff Moyer
2006-10-12 22:37 ` Andrew Morton
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=20061004111603.20cdaa35.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jmoyer@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zach.brown@oracle.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