git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Dmitry Potapov <dpotapov@gmail.com>,
	git@vger.kernel.org, Johannes Sixt <johannes.sixt@telecom.at>,
	Junio C Hamano <gitster@pobox.com>,
	Steffen Prohaska <prohaska@zib.de>
Subject: Re: [PATCH] add GIT_FAST_STAT mode for Cygwin
Date: Wed, 24 Sep 2008 08:16:53 -0700	[thread overview]
Message-ID: <20080924151653.GQ3669@spearce.org> (raw)
In-Reply-To: <81b0412b0809240809y4daa990cl5494d7b7398353f0@mail.gmail.com>

Alex Riesen <raa.lkml@gmail.com> wrote:
> 2008/9/24 Shawn O. Pearce <spearce@spearce.org>:
> >
> > However Dmitry pointed out that he has cases where this faster
> > function doesn't work correctly, and it was path specific. Some
> > areas of the filesystem work, others don't, on the same system.
> 
> Huh?! What are they? What paths require cygwin's handling
> which aren't handled already? (the absolute paths are handled).

Cygwin lets you mount a filesystem at a different part of the
filesystem.  Sort of like Linux's mount -t bind (IIRC).

For example its possible to remap C:\foo\bar\widget\srcs into
C:\cygwin\home\lib, so you see the files under /home/lib in Cygwin,
even though that folder is empty (or flat out doesn't exist)
in Windows.

That filesystem remount stuff is part of the reason why the Cygwin
stat/lstat routines are so much slower than the native Windows ones.
They have to evaluate the path space twice (once in Cygwin, again
in the Windows kernel).

-- 
Shawn.

  reply	other threads:[~2008-09-24 15:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23 14:06 [PATCH] add GIT_FAST_STAT mode for Cygwin Dmitry Potapov
2008-09-23 14:37 ` Alex Riesen
2008-09-23 16:52   ` Dmitry Potapov
2008-09-23 17:51     ` Jakub Narebski
2008-09-24 11:25     ` Alex Riesen
2008-09-24 14:03       ` Dmitry Potapov
2008-09-24 14:42         ` Alex Riesen
2008-09-24 15:02           ` Shawn O. Pearce
2008-09-24 15:09             ` Alex Riesen
2008-09-24 15:16               ` Shawn O. Pearce [this message]
2008-09-24 15:32                 ` Alex Riesen
2008-09-23 15:31 ` Shawn O. Pearce
2008-09-23 17:12   ` Dmitry Potapov
2008-09-23 19:06     ` Shawn O. Pearce
2008-09-23 20:04       ` Dmitry Potapov
2008-09-23 20:17         ` Shawn O. Pearce
2008-09-23 21:28           ` Dmitry Potapov
2008-09-23 21:58             ` Shawn O. Pearce
2008-09-23 19:03 ` Johannes Sixt
2008-09-23 19:48   ` Dmitry Potapov
2008-09-23 20:41     ` Johannes Sixt
2008-09-23 21:11       ` Dmitry Potapov
2008-09-27  7:02 ` [PATCH v2] Add a "fast stat" " Marcus Griep
2008-09-27  8:35   ` Alex Riesen
2008-09-27 10:39   ` Dmitry Potapov

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=20080924151653.GQ3669@spearce.org \
    --to=spearce@spearce.org \
    --cc=dpotapov@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=johannes.sixt@telecom.at \
    --cc=prohaska@zib.de \
    --cc=raa.lkml@gmail.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 NNTP newsgroup(s).