From: Eric Blake <eblake@redhat.com>
To: cygwin-developers@cygwin.com
Subject: Re: src/winsup/cygwin ChangeLog fhandler_proc.cc f ...
Date: Thu, 09 Oct 2014 18:07:00 -0000 [thread overview]
Message-ID: <5436CEDC.3020103@redhat.com> (raw)
In-Reply-To: <20141009174740.GA28398@calimero.vinschen.de>
[-- Attachment #1: Type: text/plain, Size: 533 bytes --]
On 10/09/2014 11:47 AM, Corinna Vinschen wrote:
> I applied another technique which has no noticable performance hit. It
> doesn't recognize all objects, only directories, symlinks, and partially
> character devices, but on the upside it uses only information which has
> already been provided anyway.
Yep, that looks a lot cleaner - reusing stuff we have for free is the
whole point of d_type optimization :)
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 539 bytes --]
prev parent reply other threads:[~2014-10-09 18:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20141009132437.7650.qmail@sourceware.org>
2014-10-09 14:31 ` Eric Blake
2014-10-09 14:51 ` Corinna Vinschen
2014-10-09 15:07 ` Eric Blake
2014-10-09 16:22 ` Corinna Vinschen
2014-10-09 17:47 ` Corinna Vinschen
2014-10-09 18:07 ` Eric Blake [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=5436CEDC.3020103@redhat.com \
--to=eblake@redhat.com \
--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).