Re: O_DIRECT wrong #define

From: Andrea Arcangeli (andrea@suse.de)
Date: Thu Jun 14 2001 - 10:51:29 EST


On Thu, Jun 14, 2001 at 03:51:12PM +0200, Andrea Arcangeli wrote:
> The O_DIRECT #define is broken:
>
> #define O_SYNC 040000
> [..]
> #define O_DIRECT 040000 /* direct disk access - should check with OSF/1 */
>
> I got a bugreport yesterday about O_SYNC returning -EINVAL because of
> that.
>
> Do you know how Digital Unix defines O_DIRECT so we can try to be binary
> compatible (in case Digital unix also enforces a softblocksize alignment
> and size on the buffer?)?

the unregistered O_ATOMICALLOC uses 0100... so I guess we should set
O_DIRECT to 02000000 unless tru64 set it to > 02000000.

Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-alpha" in
the body of a message to majordomo@vger.kernel.org



This archive was generated by hypermail 2b29 : Fri Jun 15 2001 - 21:00:27 EST