From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] TEST RELEASE: Cygwin 2.3.0-0.4
Date: Tue, 27 Oct 2015 10:10:00 -0000 [thread overview]
Message-ID: <20151027092722.GN5319@calimero.vinschen.de> (raw)
In-Reply-To: <562E4ED0.7020907@Nexgo.DE>
[-- Attachment #1: Type: text/plain, Size: 1743 bytes --]
On Oct 26 17:03, Achim Gratz wrote:
> Am 26.10.2015 um 11:07 schrieb Corinna Vinschen:
> >Erm, really? I tested this locally with a directory with hundreds
> >of files, each of which belonged to another user or group, and that
> >resulted in a 25% slowdown. Not 1000%. Oh boy.
>
> That test is almost as bad as it can ever get. Given that enumerating all
> AD accouts with mkpasswd takes about 2 hours and I'm doing something very
> similar here, I'm not even surprised. I was more surprised to see the
> server go so fast, but my guess is that it can use jumbo frames to talk to
> the AD.
Ok, so you don't seem to think this is a major drawback.
> >>While that hurts, the more usual case with many files from the
> >>same user doesn't feel any slower at the moment. The access through VPN
> >>will be interesting, though...
> >
> >Did you try this in the meantime?
>
> No, sorry.
No worries. I'm mulling over the idea to release 2.3.0 this week
without the new ACL handling code to get the latest fixes out of the
door first and push this stuff into a 2.4.0 release in November.
> >Given the above result, I'm wondering if we can afford using AuthZ at
> >all. OTOH I don't see any other way to get the correct POSIX permissions
> >from a non-Cygwin ACL :(
>
> If you really want fast but incorrect there's always the "noacl" mount
> option.
Right. OTOH, maybe we could enhance the "acl" mount option?
"acl" -> "quickacl" -> "noacl"?
> --
> Achim.
>
> (on the road :-)
https://www.youtube.com/watch?v=qRKNw477onU
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Red Hat
[-- Attachment #2: Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-10-27 9:27 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 1:52 Corinna Vinschen
2015-10-23 12:35 ` Achim Gratz
2015-10-23 12:55 ` Corinna Vinschen
2015-10-23 13:10 ` Corinna Vinschen
2015-12-21 13:23 ` Thomas Wolff
2015-12-21 15:01 ` Corinna Vinschen
2015-10-23 14:52 ` Achim Gratz
2015-10-26 11:13 ` Corinna Vinschen
2015-10-26 16:14 ` Achim Gratz
2015-10-27 10:10 ` Corinna Vinschen [this message]
2015-10-27 13:28 ` Achim Gratz
2015-10-27 15:11 ` Corinna Vinschen
2015-12-06 9:58 ` Achim Gratz
2015-12-06 14:08 ` Corinna Vinschen
2015-12-06 14:29 ` Achim Gratz
2015-12-06 19:04 ` Corinna Vinschen
2015-12-06 19:50 ` Achim Gratz
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=20151027092722.GN5319@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@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).