9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] iounit: bump it across the board
Date: Thu, 09 Jun 2022 09:40:52 -0400	[thread overview]
Message-ID: <F1388103CC957DBB7A7B7B5E2370147A@eigenstate.org> (raw)
In-Reply-To: <B1CE2CB62E636234B81AB03108522165@eigenstate.org>

Quoth ori@eigenstate.org:
> Quoth noam@pixelhero.dev:
> > Quoth ori@eigenstate.org:
> > > This patch bumps up the iounit in the kernel to 32k, and
> > > introduces the IOUNIT constant to take advantage of it.
> > 
> > Any reason I shouldn't bump it to 1M or something locally?
> > (in the kernel and, in userspace, in non-libthread applications)
> > 
> > - Noam Preil
> > 
> Try it out, but keep in mind that on a slower connection,
> you have to wait for the entire iounit to get sent before
> you can send the next request -- so, eg, tethering over
> wifi means that your file IO needs to go through fully
> before your next mouse message can get sent.

phrased poorly -- but, if your mouse and file system share
a 9p channel (ie, exportfs), then large messages will block
all other communication.

the other reason is that you can have a lot of in flight
9p buffers at once; up to 64k per connection. Most of the
time there will be fewer, but not always. But even a few
hundred 1 meg buffers is a lot of memory on smaller modern

  reply	other threads:[~2022-06-09 13:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-09  3:47 ori
2022-06-09  4:42 ` noam
2022-06-09 13:36   ` ori
2022-06-09 13:40     ` ori [this message]
2022-06-09 14:10       ` hiro
2022-06-09 15:08       ` noam
2022-06-09 16:31         ` ori
2022-07-03  0:41           ` ori

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=F1388103CC957DBB7A7B7B5E2370147A@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9front@9front.org \


* 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).