From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] How is smp handled in file services?
Date: Fri, 13 Mar 2020 17:25:49 +0100 [thread overview]
Message-ID: <CAFSF3XOHbjaenxU69YjCj9nFYQZijaUVTVntns-a9N19X+EtMA@mail.gmail.com> (raw)
In-Reply-To: <A54D7D7F98CD4432C351CDCF65C9F170@eigenstate.org>
latency is not *due* to 9p.
9p is slow *due* to latency.
if at all.
try random disk access latency on linux. it's magnitudes worse.
bandwidth is low, yes. and that is because right now 9p doesn't help
you keep the buffers full.
prev parent reply other threads:[~2020-03-13 16:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-10 23:49 Trevor Higgins
2020-03-11 1:03 ` [9front] " ori
2020-03-11 2:22 ` Trevor Higgins
2020-03-11 2:28 ` ori
2020-03-13 16:25 ` hiro [this message]
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=CAFSF3XOHbjaenxU69YjCj9nFYQZijaUVTVntns-a9N19X+EtMA@mail.gmail.com \
--to=23hiro@gmail.com \
--cc=9front@9front.org \
/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).