This is the mail archive of the cygwin-developers@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] |
On Thu, 2002-08-22 at 06:14, Conrad Scott wrote: > > On my m/c, a 900Mhz Pentium III (?), the same test program I was > using for the __stdcall / regparm testing (read 16Mb from > /dev/zero one byte at a time and write to /dev/zero) takes about 3 > seconds longer with the readv/writev changes. That is, ~38.6 > seconds rather than ~35.6 seconds. So, it's measurable but it's a > pretty extreme test. how long does it take if you read in a readv block of, say 1000 elements? Faster or slower? > Does anyone feel this is important? If so, I can write separate > code paths for both read/write as well as readv/writev, which > would then be no slower than the current DLL code. The issue then > is a small increase in DLL size along with more duplicate code to > maintain. > > Any votes? 1) Implement a clean design. 2) *IF* the readv->read code is fairly short, put it in a header so it can inline when appropriate. 3) Implement 'native' Overlapped IOw/ scatter-gather for NT OS's on disk files. :}. Rob
Attachment:
signature.asc
Description: This is a digitally signed message part
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |