This is the mail archive of the
mailing list for the Cygwin project.
Re: slow share = slow scripts?
On Fri, May 26, 2006 at 10:37:52AM -0500, mwoehlke wrote:
>Gary R. Van Sickle wrote:
>>> Also, why *is*
>>>fstat() so inefficient?
>>Short answer: because it gets a bunch of information about the file that
>>isn't necessarily available without hitting (open()ing) the file itself.
>Like... what? Inode information? Looking at the man page for 'stat' (on
>Linux, anyway; apparently I don't have the libc man pages installed on
>Cygwin), I don't see anything that I would expect to need to *open* the
>file to retrieve.
>Way way back in the OP, I mentioned that Interix doesn't have this
>problem, which would imply a "design flaw" in Cygwin. Maybe (probably)
>it is a *necessary* design flaw, BUT...
A "necessary" design flaw? Interesting concept.
>Please note that I'm not asking anyone to do this... given the response
>I got last time, I don't have any illusions that this will happen short
>of my doing it myself (at which point I will be derided, and my work
>will never leave my office). However, I would appreciate any existing
>knowledge, or even pointers to where to start poking around, that anyone
>would care to share.
I think that most of the pointers and insight about what Cygwin does with
fstat are all nicely encapsulated in the source code, specifically
fhandler_disk_file.cc and fhandler.cc .
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html