> " " == Chuck Lever <[EMAIL PROTECTED]> writes:
> the default behavior is that close() waits for all write-backs
> to be committed to the server's disk. you might add support
> for the "nocto" mount option so that waiting is skipped for
> shared mmap'd files, but then wh
the default behavior is that close() waits for all write-backs to
be committed to the server's disk. you might add support for the
"nocto" mount option so that waiting is skipped for shared mmap'd
files, but then what happens to data that is pinned on the client
because a write-back failed after
Hi,
Linus was not too keen on the patches that circulated last week. In
his concept of shared mmap(), he wants it to ignore the usual
requirement we have on normal files whereby we flush out the pages on
file close. The problem is, though, that we need at least to schedule
the writes using the
3 matches
Mail list logo
