From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] iounit: bump it across the board
Date: Thu, 09 Jun 2022 12:31:44 -0400 [thread overview]
Message-ID: <CF0C885AF8F847AD65D244562BE5ACFA@eigenstate.org> (raw)
In-Reply-To: <41499E0C845E5125DEB144C0198E2753@pixelhero.dev>
Quoth noam@pixelhero.dev:
>
> Are those buffers static? If they're dynamically allocated, I
> doubt it'd be an issue; I'm thinking of a use case where e.g.
> file systems use large iounit but drivers use a small one.
>
> That seems best of both worlds: minimal consumption where more
> isn't needed, higher resource usage where it's beneficial and
> cheap.
Try it out and report back -- tuning this easily is why I added
the constant to libc.
next prev parent reply other threads:[~2022-06-09 16:33 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
2022-06-09 14:10 ` hiro
2022-06-09 15:08 ` noam
2022-06-09 16:31 ` ori [this message]
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:
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=CF0C885AF8F847AD65D244562BE5ACFA@eigenstate.org \
--to=ori@eigenstate.org \
--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).