From: Andrey Repin <anrdaemon@yandex.ru>
To: Martin Wege <martin.l.wege@gmail.com>, cygwin@cygwin.com
Subject: Re: rfe: CYGWIN fslinktypes option? Re: Catastrophic Cygwin find . -ls, grep performance on samba share compared to WSL&Linux
Date: Fri, 22 Dec 2023 21:53:39 +0300 [thread overview]
Message-ID: <1502052023.20231222215339@yandex.ru> (raw)
In-Reply-To: <CANH4o6OjJJZQkbELt+H3WdAxQbLGZ1DL0ytevknRpbTO9sVUig@mail.gmail.com>
Greetings, Martin Wege!
> The root cause is IMO the extra Win32 syscalls (>= 3 per file lookup,
> compared to 1 on Linux) to lookup the *.lnk and *.exe.lnk files on
> filesystems which have native link support (NTFS, ReFS, SMBFS, NFS).
Except you require elevation to actually create symlinks.
Or some special system configuration.
> On SMBFS and NFS it hurts the most, because access latency is the
> highest for networked filesystems.
> So my proposal would be to add an option ('fslinktypes') to the CYGWIN
> environment variable to define which types of links are supported:
> default 'all'. which is an shortcut for 'native,lnk,lnkexe'.
> So in case people do not want 'lnk' link support they just add
> CYGWIN+=' fslinktypes:native' to env, to turn off support for
> lnk/lnk.exe style links, and be happy.
> @Corinna Vinschen Would that be acceptable?
Make a patch to begin discussion.
Also, not all mangling is meaningful to disable. F.e. disabling .exe magic on
Windows would be surprising to the end user.
--
With best regards,
Andrey Repin
Friday, December 22, 2023 21:50:58
Sorry for my terrible english...
prev parent reply other threads:[~2023-12-22 19:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-06 4:08 Dan Shelton
2023-12-18 6:22 ` Dan Shelton
2023-12-18 6:49 ` Marco Atzeri
2023-12-18 6:53 ` Dan Shelton
2023-12-18 7:05 ` Marco Atzeri
2023-12-18 7:16 ` Dan Shelton
2023-12-18 8:23 ` Marco Atzeri
2023-12-20 17:20 ` Kaz Kylheku
2023-12-21 12:16 ` rfe: CYGWIN fslinktypes option? " Martin Wege
2023-12-21 16:10 ` Cedric Blancher
2023-12-21 17:43 ` Brian Inglis
2023-12-21 20:32 ` Kaz Kylheku
2023-12-24 0:47 ` Roland Mainz
2024-01-08 14:53 ` Corinna Vinschen
2023-12-22 18:53 ` Andrey Repin [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=1502052023.20231222215339@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=cygwin@cygwin.com \
--cc=martin.l.wege@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 read-only IMAP folder(s) and NNTP newsgroup(s).