X-Spam-Check-By: sourceware.org
Date: Fri, 26 May 2006 12:23:54 -0400
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: slow share = slow scripts?
Message-ID: <20060526162354.GA7151@trixie.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <e54ihh$hnf$2@sea.gmane.org> <001c01c6806d$a1249e40$020aa8c0@DFW5RB41> <e577ch$6p3$1@sea.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <e577ch$6p3$1@sea.gmane.org>
User-Agent: Mutt/1.5.11
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie.com@cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe@cygwin.com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin@cygwin.com>
List-Help: <mailto:cygwin-help@cygwin.com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Delivered-To: mailing list cygwin@cygwin.com

On Fri, May 26, 2006 at 10:37:52AM -0500, mwoehlke wrote:
>Gary R. Van Sickle wrote:
>>>From: mwoehlke
>>[snip]
>>> 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 .

cgf

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

