lkml.org 
[lkml]   [2002]   [Aug]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
SubjectRE: O_SYNC option doesn't work (2.4.18-3)
From
>>>>> " " == Gregory Giguashvili <Gregoryg@ParadigmGeo.com> writes:

> File locking, meaning lockd? There are so many problems with
> file locking in heterogeneous environments that we were moving
> towards dropping its usage. Instead, we planned to use some
> home grown TCP based lock server mechanism.

> I understand that locking file flushes NFS cache, isn't it? Why
> can't it be flushed by O_SYNC and "sync" options presence? This
> would make the life much easier for programmers...

Tough. The above is not part of the O_SYNC spec on any platform and I
have no intention of implementing it.

The sort of thing you would like to do will be possible with O_DIRECT
(which is a design to allow user programs to manage their own
caches). That has yet to be integrated into the standard kernel
though.

Cheers,
Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:27    [W:0.031 / U:2.996 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site