From: Christopher Faylor <cgf@redhat.com>
To: cygwin@cygwin.com
Subject: Re: pipe improvements in snapshot
Date: Wed, 11 Dec 2002 11:46:00 -0000 [thread overview]
Message-ID: <20021211193553.GA30532@redhat.com> (raw)
In-Reply-To: <20021211192639.GE29798@redhat.com>
On Wed, Dec 11, 2002 at 02:26:39PM -0500, Christopher Faylor wrote:
>On Wed, Dec 11, 2002 at 03:08:45PM +0100, thomas wrote:
>>Christopher Faylor <cgf-cygwin@cygwin.com> wrote:
>>
>>> Please check out the latest snapshot and report here if there are
>>> problems. I haven't yet tried this on Windows 9x class systems so it's
>>> entirely possible that there is a problem there.
>>
>>It seems to work great! I did a few tests and there was no delay anymore
>>whatsoever. I've just sent the dll to someone to try out on a 9x system.
>
>I'll test this on 9x myself eventually. With gritted teeth...
>
>>One thing about the possible data loss: Is that true data loss, like
>>some bytes won't make it trough the pipe, or will that only result in a
>>delay because the bytes have to be send again?
>
>It's true data loss but it is very very unlikely that it will ever be hit.
>I thought I would get this out there while I ruminated on ways to eliminate
>the potential for loss.
>
>>I will do some more thourough tests and will report back.
>>
>>Thanks so far!
>
>You're welcome.
Btw, thanks for the feedback. It's an interesting datapoint. It seems
to mean that the context switch implicit in introducing a thread into
the pipe read is substantially less than the 10ms delay we were adding
in the old scheme. This probably makes sense but... this is Windows,
so....
cgf
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next prev parent reply other threads:[~2002-12-11 19:34 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 0:48 Christopher Faylor
2002-12-11 6:27 ` thomas
2002-12-11 8:02 ` thomas
2002-12-11 11:35 ` Christopher Faylor
2002-12-11 11:46 ` Christopher Faylor [this message]
2002-12-11 23:31 ` Ralf Habacker
2002-12-12 4:43 ` Norman Vine
2002-12-12 10:27 ` Christopher Faylor
2002-12-12 22:32 ` Norman Vine
[not found] ` <H000076f17389de6.1039774000.eux100.sgp.st.com@MHS>
2002-12-13 7:28 ` Pavel Holejsovsky
2002-12-13 22:29 ` More pipe (and other) " Christopher Faylor
2002-12-13 22:44 ` Christopher Faylor
2002-12-14 12:29 ` Christopher Faylor
2002-12-14 12:42 ` Norman Vine
[not found] ` <H000076f173b29e7.1040038646.eux100.sgp.st.com@MHS>
2002-12-16 7:49 ` Pavel Holejsovsky
2002-12-14 18:32 ` Arno Waschk
2002-12-14 19:18 ` Christopher Faylor
2002-12-15 10:01 ` Arno Waschk
2002-12-15 11:16 ` Christopher Faylor
2002-12-15 13:07 ` Randall R Schulz
[not found] ` <H000076f1736db55.1039696329.eux100.sgp.st.com@MHS>
2002-12-12 6:39 ` pipe " Pavel Holejsovsky
2002-12-11 16:20 fergus
2002-12-11 23:22 ` Gary R. Van Sickle
2002-12-12 4:08 Elfyn McBratney
2002-12-12 4:23 Elfyn McBratney
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=20021211193553.GA30532@redhat.com \
--to=cgf@redhat.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).