Cygwin: api docs: add missing fallocate
Also add notes in terms of fallocate quirks. Signed-off-by: Corinna Vinschen <corinna@vinschen.de>
This commit is contained in:
parent
241b50a7ab
commit
4ecfb5b729
|
@ -1314,6 +1314,7 @@ also IEEE Std 1003.1-2017 (POSIX.1-2017).</para>
|
||||||
exp10
|
exp10
|
||||||
exp10f
|
exp10f
|
||||||
exp10l
|
exp10l
|
||||||
|
fallocate (see <xref linkend="std-notes">chapter "Implementation Notes"</xref>)
|
||||||
fcloseall
|
fcloseall
|
||||||
fcloseall_r
|
fcloseall_r
|
||||||
fedisableexcept
|
fedisableexcept
|
||||||
|
@ -1755,6 +1756,14 @@ RLIMIT_CORE and RLIMIT_STACK return the current values and set the requested
|
||||||
values.
|
values.
|
||||||
All other resource arguments return -1 and set EINVAL.</para>
|
All other resource arguments return -1 and set EINVAL.</para>
|
||||||
|
|
||||||
|
<para><function>fallocate</function> has a few Windows quirks: The
|
||||||
|
FALLOC_FL_ZERO_RANGE operation is NOT atomic. With flags set to 0 and
|
||||||
|
FALLOC_FL_KEEP_SIZE, sparse blocks in the given range are re-allocated
|
||||||
|
as per the POSIX requirements. This re-allocation operation isn't
|
||||||
|
atomic either. Over-allocation with FALLOC_FL_KEEP_SIZE is only
|
||||||
|
temporary on Windows until the last handle to the file is closed.
|
||||||
|
Over-allocation on sparse files is entirely ignored on Windows.</para>
|
||||||
|
|
||||||
</sect1>
|
</sect1>
|
||||||
|
|
||||||
</chapter>
|
</chapter>
|
||||||
|
|
Loading…
Reference in New Issue