[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH 08/13] 9p: darwin: Ignore O_{NOATIME, DIRECT}
From: |
Keno Fischer |
Subject: |
Re: [Qemu-devel] [PATCH 08/13] 9p: darwin: Ignore O_{NOATIME, DIRECT} |
Date: |
Thu, 31 May 2018 12:35:02 -0400 |
>
> Please don't kill the spaces.
>
Sorry, will undo. My editor has strong opinions about styling.
>> +#ifndef CONFIG_DARWIN
>> + {P9_DOTL_NOATIME, O_NOATIME},
>> + /* On Darwin, we could map to F_NOCACHE, which is
>> + similar, but doesn't quite have the same
>> + semantics. However, we don't support O_DIRECT
>
> But are these semantics worse than dumping the flag ?
>
I don't know. I looked around a bit and most OS abstraction
layers tend to not do this translation automatically:
https://github.com/libuv/libuv/issues/1600
>> + even on linux at the moment, so we just ignore
>> + it here. */
>
> Yeah, and I doubt we'll ever support it on linux either. But,
> anyway, why filter these out ? Do they cause a build break ?
>
Yes, neither O_DIRECT nor O_NOATIME are defined on Darwin,
so trying to use them causes errors.
- Re: [Qemu-devel] [PATCH 06/13] 9p: darwin: Address minor differences, (continued)
[Qemu-devel] [PATCH 07/13] 9p: darwin: Properly translate AT_REMOVEDIR flag, keno, 2018/05/26
[Qemu-devel] [PATCH 08/13] 9p: darwin: Ignore O_{NOATIME, DIRECT}, keno, 2018/05/26
[Qemu-devel] [PATCH 09/13] 9p: darwin: Provide a compatibility definition for XATTR_SIZE_MAX, keno, 2018/05/26
[Qemu-devel] [PATCH 10/13] 9p: darwin: *xattr_nofollow implementations, keno, 2018/05/26
[Qemu-devel] [PATCH 11/13] 9p: darwin: Mark mknod as unsupported, keno, 2018/05/26