From: beto@ncube.com beto@ncube.com
Subject: [9fans] IL question?
Date: Thu, 16 Oct 1997 16:40:26 -0700 [thread overview]
Message-ID: <19971016234026._qeF82bU4ZNJg4tB0nlKRB_cQC42bYlnbVmCCPUR8Q8@z> (raw)
Hi,
IL does not have any flow control, I know
it was design for RPC type comunication, but if
a user starts writing a lot of data down an IL
connection it would use all kernel memory :-(.
Has this been fixed in Brazil? How?
I don't think it's good idea to add very complex flow control
scheme to avoid this problem. stiloput could check the
noacked queue and limit the number of packets a given user can
have outstanding.
Any comments would be appreciate?
next reply other threads:[~1997-10-16 23:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-10-16 23:40 beto [this message]
1997-10-17 4:33 Rich
1997-10-17 16:50 beto
1997-10-17 17:09 presotto
1997-10-17 17:36 beto
1997-10-17 17:46 presotto
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=19971016234026._qeF82bU4ZNJg4tB0nlKRB_cQC42bYlnbVmCCPUR8Q8@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).