xfs
[Top] [All Lists]

Re: [patch 0/9] writeback data integrity and other fixes (take 3)

To: jim owens <jowens@xxxxxx>
Subject: Re: [patch 0/9] writeback data integrity and other fixes (take 3)
From: Jim Rees <rees@xxxxxxxxx>
Date: Thu, 30 Oct 2008 09:41:18 -0400
Cc: Nick Piggin <npiggin@xxxxxxx>, Chris Mason <chris.mason@xxxxxxxxxx>, Ric Wheeler <ricwheeler@xxxxxxxxx>, Jamie Lokier <jamie@xxxxxxxxxxxxx>, Christoph Hellwig <hch@xxxxxxxxxxxxx>, linux-nfs@xxxxxxxxxxxxxxx, akpm@xxxxxxxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx
In-reply-to: <4909ADE0.1060205@xxxxxx>
References: <20081029031645.GE4985@disturbed> <20081029091203.GA32545@xxxxxxxxxxxxx> <20081029092143.GA5953@xxxxxxxxxxxxx> <20081029094417.GA21824@xxxxxxxxxxxxx> <20081029103029.GC5953@xxxxxxxxxxxxx> <20081029122234.GE846@xxxxxxxxxxxxx> <490865E3.8070102@xxxxxxxxx> <1225292196.6448.263.camel@xxxxxxxxxxxxxxxxxxxx> <20081030021601.GF18041@xxxxxxxxxxxxx> <4909ADE0.1060205@xxxxxx>
jim owens wrote:

  AFAIK the fsync semantic comes from the days of dinosaurs,
  mainframes, and minicomputers... when a lot of operating
  systems had user-space libraries that buffered the I/O.
  On fsync(fd), the "fd2" data would still be in user-space.

User space buffering happens in stdio, which is above the system call
level.  It's been that way since fsync() was first introduced, and is still
that way today.

<Prev in Thread] Current Thread [Next in Thread>