From: forsyth@plan9.cs.york.ac.uk forsyth@plan9.cs.york.ac.uk
Subject: faster u9fs
Date: Fri, 15 Sep 1995 13:22:07 -0400 [thread overview]
Message-ID: <19950915172207.1VAqg3WHLlwKpq0fii84AmtAI89SPWVLkhmWVs2Zqgo@z> (raw)
if your unix tcp/ip implementation has the TCP_NODELAY option,
try enabling it in u9fs:
int one = 1;
setsockopt(fd, IPPROTO_TCP, TCP_NODELAY, &one, sizeof(one));
you'll have to scour the heap of include files in /usr/include
to find the one with the TCP_NODELAY option in it.
i found it made a difference on our rs/6000 systems.
9P uses many small reply messages, which are subject to the delay.
(the system waits to see if more data turns up to make the
packet really worthwhile, but in this case it just makes it less responsive.)
reply other threads:[~1995-09-15 17:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19950915172207.1VAqg3WHLlwKpq0fii84AmtAI89SPWVLkhmWVs2Zqgo@z \
--to=forsyth@plan9.cs.york.ac.uk \
/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).