On Jun 6 19:28, Christopher Faylor wrote: > On Mon, Jun 07, 2010 at 12:12:36AM +0200, Matthias Andree wrote: > >Meaning that: even if I'm only a Cygwin user, and I'm sometimes > >disappointed by how slow it is, too, I'm sort of convinced there isn't a > >cheaper way to get all the required information. > > I'm disappointed in Cygwin's slowness too. Corinna and I have spent > many hours pouring over MSDN, internals books, and internals web sites. > I've spent time looking at ReactOS sources trying to see if they would > provide any insight into how Windows does things. > > It's possible, maybe even likely, that there are things that could be > done to speed up Cygwin but I don't think it's likely that they include > using simple Windows API stuff like the suggested GetFileAttributes() or > limiting Cygwin's POSIXness.
Full ACK. > And, if speed ups do exist, they > definitely do not require a private audience with me or Corinna. > > The best place to discuss improvements is actually the cygwin-developers > mailing list. And, as I said, if you do have a patch to propose, it > would pay to start early on getting the paperwork done. Indeed. It would be rather cool if some interested developer would dive into this code and maybe just look from a different perspective. I don't like the idea to cripple the stat API, though. There's certainly room for improvement in other ways while maintaining information completeness of the stat function. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
