Re: [patch] call truncate_inode_pages in the DIO fallback to buffered I/O path

> 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.

This was noticed as a distro regression as they moved from the kernels
that used to invalidate the entire address space on direct io ops to
more modern ones that only invalidate the region being written.

You can end up with significant memory pressure after this change with a
large enough working set on disk.

> eek.  truncate_inode_pages() will throw away dirty data.  Very dangerous,
> much chin-scratching needed.

Yeah, I failed to tell Jeff that it should be calling
filemap_fdatawrite() first to get things into writeback.  (And
presumably not truncating if that returns an error.)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: [patch] call truncate_inode_pages in the DIO fallback to buffered I/O path
  - From: Jeff Moyer <[email protected]>

References:
- [patch] call truncate_inode_pages in the DIO fallback to buffered I/O path
  - From: Jeff Moyer <[email protected]>
- Re: [patch] call truncate_inode_pages in the DIO fallback to buffered I/O path
  - From: Andrew Morton <[email protected]>

Prev by Date: Re: [patch 02/23] GTOD: persistent clock support, core
Next by Date: Re: Directories > 2GB
Previous by thread: Re: [patch] call truncate_inode_pages in the DIO fallback to buffered I/O path
Next by thread: Re: [patch] call truncate_inode_pages in the DIO fallback to buffered I/O path
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]