This is the mail archive of the cygwin-patches@cygwin.com mailing list for the Cygwin project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Performance: fhandler_socket and ready_for_read()

From: "Conrad Scott" <Conrad dot Scott at dsl dot pipex dot com>
To: <cygwin-patches at cygwin dot com>
Date: Wed, 31 Jul 2002 03:20:37 +0100
Subject: Re: Performance: fhandler_socket and ready_for_read()
References: <07f001c2381e$43118070$6132bc3e@BABEL> <20020731002910.GD17985@redhat.com> <086701c2382f$2c6b19b0$6132bc3e@BABEL> <20020731012133.GB21134@redhat.com> <08e301c23833$d05627f0$6132bc3e@BABEL> <20020731020213.GC21291@redhat.com>

"Christopher Faylor" <cgf@redhat.com> wrote:
> I think we're narrowing it down, though.  :-)

I don't see how it can escape our clutches much longer, however
much it wriggles and moans :-)

// Conrad

Follow-Ups:
- Re: Performance: fhandler_socket and ready_for_read()
  - From: Christopher Faylor

References:
- Performance: fhandler_socket and ready_for_read()
  - From: Conrad Scott
- Re: Performance: fhandler_socket and ready_for_read()
  - From: Christopher Faylor
- Re: Performance: fhandler_socket and ready_for_read()
  - From: Conrad Scott
- Re: Performance: fhandler_socket and ready_for_read()
  - From: Christopher Faylor
- Re: Performance: fhandler_socket and ready_for_read()
  - From: Conrad Scott
- Re: Performance: fhandler_socket and ready_for_read()
  - From: Christopher Faylor

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]