On Fri, Jan 11, 2019 at 08:36:55AM +0100, Jiri Kosina wrote:
On Thu, 10 Jan 2019, Dave Chinner wrote:
quoted
Sounds nice from a theoretical POV, but reality has taught us very
different lessons.
FWIW, a quick check of XFS's history so you understand how long this
behaviour has been around. It was introduced in the linux port in 2001
as direct IO support was being added:
commit e837eac23662afae603aaaef7c94bc839c1b8f67
Author: Steve Lord [off-list ref]
Date: Mon Mar 5 16:47:52 2001 +0000
Add bounds checking for direct I/O, do the cache invalidation for
data coherency on direct I/O.
Out of curiosity, which repository is this from please? Even google
doesn't seem to know about this SHA.
because oss.sgi.com is no longer with us, it's fallen out of all the
search engines. It was from the "archive/xfs-import.git" tree on
oss.sgi.com:
https://web.archive.org/web/20120326044237/http://oss.sgi.com:80/cgi-bin/gitweb.cgi
but archive.org doesn't have a copy of the git tree. It contained
the XFS history right back to the first Irix commit in 1993. Some of
us still have copies of it sitting around....
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com