From: Roland Mainz <roland.mainz@nrubsig.org>
To: cygwin-developers@cygwin.com
Subject: Re: SEEK_HOLE Support in Cygwin?
Date: Fri, 25 Aug 2023 13:09:09 +0200 [thread overview]
Message-ID: <CAKAoaQkY0P5xsVWciyT-_-waeVK-2QWSCz9znU577nW3uLNaaQ@mail.gmail.com> (raw)
In-Reply-To: <ZOhu9KTudSS9fbw3@calimero.vinschen.de>
On Fri, Aug 25, 2023 at 11:05 AM Corinna Vinschen
<corinna-cygwin@cygwin.com> wrote:
>
> On Aug 24 14:03, Roland Mainz wrote:
> > Question for Corinna:
>
> Everybody involved in the project could answer this question, but...
>
> > Does Cygwin support allocation/deallocation of filesystem blocks via
> > Linux's |fallocate()|-API ?
>
> ...just try this:
>
> $ cat > a.c <<EOF
> extern void fallocate();
> extern void posix_fallocate();
>
> int main()
> {
> fallocate();
> posix_fallocate();
> }
> EOF
> $ gcc -o a a.c
Thanks...
... I saw that the functions are there, but my question was more like
"supports"=="calls native Windows API".
|fallocate()| support seems to be in
./newlib-cygwin/winsup/cygwin/fhandler/disk_file.cc, and supports the
allocation of blocks - but I couldn't find support for
|FALLOC_FL_PUNCH_HOLE|, e.g. deallocation of blocks (to "punch" a hole
into the file).
Is this an oversight, or does Window's native API not support that ?
> In fact, we have a list of supported APIs: https://cygwin.com/cygwin-api/
Thanks
----
Bye,
Roland
--
__ . . __
(o.\ \/ /.o) roland.mainz@nrubsig.org
\__\/\/__/ MPEG specialist, C&&JAVA&&Sun&&Unix programmer
/O /==\ O\ TEL +49 641 3992797
(;O/ \/ \O;)
next prev parent reply other threads:[~2023-08-25 11:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-06 17:14 Cedric Blancher
2023-08-07 8:33 ` Corinna Vinschen
2023-08-09 15:30 ` Corinna Vinschen
2023-08-10 2:43 ` Cedric Blancher
2023-08-10 8:28 ` Corinna Vinschen
2023-08-21 4:33 ` Cedric Blancher
2023-08-21 8:32 ` Corinna Vinschen
2023-08-24 12:03 ` Roland Mainz
2023-08-25 9:05 ` Corinna Vinschen
2023-08-25 11:09 ` Roland Mainz [this message]
2023-08-25 11:23 ` Corinna Vinschen
2023-08-25 11:43 ` Corinna Vinschen
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=CAKAoaQkY0P5xsVWciyT-_-waeVK-2QWSCz9znU577nW3uLNaaQ@mail.gmail.com \
--to=roland.mainz@nrubsig.org \
--cc=cygwin-developers@cygwin.com \
/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: link
Be 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).