public inbox for cygwin-cvs@sourceware.org help / color / mirror / Atom feed
From: Corinna Vinschen <corinna@sourceware.org> To: cygwin-cvs@sourceware.org Subject: [newlib-cygwin/main] Cygwin: api docs: add missing fallocate Date: Mon, 15 Jan 2024 10:05:20 +0000 (GMT) [thread overview] Message-ID: <20240115100521.22F983858C41@sourceware.org> (raw) https://sourceware.org/git/gitweb.cgi?p=newlib-cygwin.git;h=4ecfb5b7292af4baf0a2f199f5351b67c8faf4cc commit 4ecfb5b7292af4baf0a2f199f5351b67c8faf4cc Author: Corinna Vinschen <corinna@vinschen.de> AuthorDate: Mon Jan 15 11:03:48 2024 +0100 Commit: Corinna Vinschen <corinna@vinschen.de> CommitDate: Mon Jan 15 11:04:29 2024 +0100 Cygwin: api docs: add missing fallocate Also add notes in terms of fallocate quirks. Signed-off-by: Corinna Vinschen <corinna@vinschen.de> Diff: --- winsup/doc/posix.xml | 9 +++++++++ 1 file changed, 9 insertions(+) diff --git a/winsup/doc/posix.xml b/winsup/doc/posix.xml index 151aeb9fee2b..1a4eee1ab1b8 100644 --- a/winsup/doc/posix.xml +++ b/winsup/doc/posix.xml @@ -1314,6 +1314,7 @@ also IEEE Std 1003.1-2017 (POSIX.1-2017).</para> exp10 exp10f exp10l + fallocate (see <xref linkend="std-notes">chapter "Implementation Notes"</xref>) fcloseall fcloseall_r fedisableexcept @@ -1755,6 +1756,14 @@ RLIMIT_CORE and RLIMIT_STACK return the current values and set the requested values. 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> </chapter>
reply other threads:[~2024-01-15 10:05 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20240115100521.22F983858C41@sourceware.org \ --to=corinna@sourceware.org \ --cc=cygwin-cvs@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).