From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Implementing /bin/ionice, ioprio_set() support with FILE_IO_PRIORITY_HINT_INFO?
Date: Wed, 3 Apr 2024 10:39:18 +0200 [thread overview]
Message-ID: <Zg0Vthvgez0sviLk@calimero.vinschen.de> (raw)
In-Reply-To: <CANH4o6OG8-ewHbxux+ed7FG4Xwe48eiEK_TQe8eQyvY3JVUDBw@mail.gmail.com>
On Apr 3 03:51, Martin Wege via Cygwin wrote:
> Hello,
>
> could Cygwin implement support for /usr/bin/ionice and ioprio_set()
> via FILE_IO_PRIORITY_HINT_INFO?
Not ionice, the tool, but only ioprio_get/ioprio_set, the API.
The problem is the functionality bit allowing to set the priority
in arbitrary processes.
And, as usual, https://cygwin.com/acronyms/#SHTDI
I would again like to stress the fact that we're all volunteers here,
and we're a sadly small bunch of people actually contributing to the
core code.
It's easy to ask for new functionality, but it needs time to implement
stuff and we all have another job keeping the money coming, and that
job takes priority.
We don't want to see stuff like the xz debacle in Cygwin, right?
Corinna
prev parent reply other threads:[~2024-04-03 8:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 1:51 Implementing /bin/ionice,ioprio_set() " Martin Wege
2024-04-03 8:39 ` Corinna Vinschen [this message]
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=Zg0Vthvgez0sviLk@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@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).