From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin-patches@cygwin.com
Subject: Re: [PATCH 0/1] Fix fstat on FIFOs, part 1
Date: Tue, 9 Feb 2021 16:25:49 +0100 [thread overview]
Message-ID: <20210209152549.GW4251@calimero.vinschen.de> (raw)
In-Reply-To: <20210209151158.57831-1-kbrown@cornell.edu>
On Feb 9 10:11, Ken Brown via Cygwin-patches wrote:
> Commit 76dca77f04 had a careless blunder, so this patch reverts it.
>
> Nevertheless, fstat(2) can be made more efficient on FIFOs, and I'm
> working on a separate patchset to do this right. It's worth doing,
> because every call to open(2) on a FIFO leads to a call chain
>
> device_access_denied --> fhaccess --> fstat,
>
> and this is one of the cases where greater efficiency is possible.
>
> Ken Brown (1):
> Revert "Cygwin: fstat_helper: always use handle in call to
> get_file_attribute"
>
> winsup/cygwin/fhandler_disk_file.cc | 7 +++----
> 1 file changed, 3 insertions(+), 4 deletions(-)
Sure, go ahead.
Thanks,
Corinna
prev parent reply other threads:[~2021-02-09 15:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 15:11 Ken Brown
2021-02-09 15:11 ` [PATCH 1/1] Revert "Cygwin: fstat_helper: always use handle in call to get_file_attribute" Ken Brown
2021-02-09 15:25 ` 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=20210209152549.GW4251@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin-patches@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).