From: beto@ncube.com beto@ncube.com
Subject: [9fans] IL question?
Date: Fri, 17 Oct 1997 10:36:20 -0700 [thread overview]
Message-ID: <19971017173620.M92tldcCPQOlRnpLmE-3WcFpK3-X6kqmScWTXyLUuAg@z> (raw)
In <199710171717.NAA18350@cse.psu.edu>
presotto@plan9.bell-labs.com wrote:
> It wouldn't take much to throw out any il data
> that appears after > 256k of il bytes are in the
> process end queue (or pick your favorite limit).
> You'll still have to process the packets or the
> protocol will break but nothing forces you to keep
> the processed data lying around.
>
thanks.
I think we'll implement something similar to
the tcp->sndfull idea. You keep a counter of bytes
on the ackq and if bigger than some limit it will
sleep. The ackto funtion will wakeup this
process if the number is smaller than half
the limit.
This shouldn't affect RPC performance and the protocol
will work as a pipe too.
next reply other threads:[~1997-10-17 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-17 17:36 beto [this message]
-- strict thread matches above, loose matches on Subject: below --
1997-10-17 17:46 presotto
1997-10-17 17:09 presotto
1997-10-17 16:50 beto
1997-10-17 4:33 Rich
1997-10-16 23:40 beto
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=19971017173620.M92tldcCPQOlRnpLmE-3WcFpK3-X6kqmScWTXyLUuAg@z \
--to=beto@ncube.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 NNTP newsgroup(s).