From: Joel Becker Date: Mon, 28 Jun 2010 19:04:20 -0700 Subject: [Ocfs2-devel] [PATCH] Revert "writeback: limit write_cache_pages integrity scanning to current EOF" In-Reply-To: <20100629015615.GZ6590@dastard> References: <20100628173529.GA10573@mail.oracle.com> <20100629002421.GY6590@dastard> <20100629005403.GC24343@mail.oracle.com> <20100629015615.GZ6590@dastard> Message-ID: <20100629020420.GE24343@mail.oracle.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Dave Chinner Cc: Linus Torvalds , Linux Kernel , ocfs2-devel@oss.oracle.com, Tao Ma , Dave Chinner , Christoph Hellwig , Mark Fasheh On Tue, Jun 29, 2010 at 11:56:15AM +1000, Dave Chinner wrote: > > Regarding XFS, how do you handle catching the tail of an > > allocation with an lseek(2)'d write? That is, your current allocation > > has a few blocks outside of i_size, then I lseek(2) a gigabyte past EOF > > and write there. The code has to recognize to zero around old_i_size > > before moving out to new_i_size, right? I think that's where our old > > approaches had problems. > > xfs_file_aio_write() handles both those cases for us via > xfs_zero_eof(). What it does is map the region from the old EOF to > the start of the new write and zeroes any allocated blocks that are > not marked unwritten that lie within the range. It does this via the > internal mapping interface because we hide allocated blocks past EOF > from the page cache and higher layers. Makes sense as an approach. We deliberately do this through the page cache to take advantage of its I/O patterns and tie in with JBD2. Also, we don't feel like maintaining an entire shadow page cache ;-) Joel -- Life's Little Instruction Book #356 "Be there when people need you." Joel Becker Consulting Software Developer Oracle E-mail: joel.becker at oracle.com Phone: (650) 506-8127