Front page | perl.perl5.porters |
Postings from May 2003
Re: Meaning of sysread()
Thread Previous
|
Thread Next
From:
Mark Mielke
Date:
May 21, 2003 09:26
Subject:
Re: Meaning of sysread()
Message ID:
20030521163229.GB25674@mark.mielke.cc
On Wed, May 21, 2003 at 12:03:45PM -0400, Horsley Tom wrote:
> > - sysread() is supposed to be a more direct system read that avoids
> > the intermediate layers of processing. This definately includes
> > STDIO, and as far as I am concerned, it definatesly includes
> > filtering.
> Which, of course, really means that on win32 it ought to be calling
> ReadFile() or ReadFileEx(), not the C library read() function which is
> as much a part of stdio on win32 as fread is :-).
My honest opinion is 'Yes please!'.
I would like to see PerlIO implemented entirely in terms of WIN32
system calls. File descriptors only need to be allocated for sockets,
or if fileno() is invoked. For everything else, HANDLE is my
preference.
Perhaps some of my opinion is a result of my regular observations that
things run several times slower on Windows than on Unix, and the
knowledge I have that although Windows is inherently slower in some
regards, in other regards, such as I/O, it may be more efficient. The
'layers of emulation' such as you point out are what makes it so slow.
Cheers,
mark
--
mark@mielke.cc/markm@ncf.ca/markm@nortelnetworks.com __________________________
. . _ ._ . . .__ . . ._. .__ . . . .__ | Neighbourhood Coder
|\/| |_| |_| |/ |_ |\/| | |_ | |/ |_ |
| | | | | \ | \ |__ . | | .|. |__ |__ | \ |__ | Ottawa, Ontario, Canada
One ring to rule them all, one ring to find them, one ring to bring them all
and in the darkness bind them...
http://mark.mielke.cc/
Thread Previous
|
Thread Next