From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] cfs, aan and network recommendations
Date: Fri, 19 Nov 2021 00:21:30 +0100 [thread overview]
Message-ID: <CAFSF3XOySmsf6z9pv+HAx8fVmTK+YXz_a2caZBNNosNZNn2Bsw@mail.gmail.com> (raw)
In-Reply-To: <4A0B108C-C61D-48F4-9550-6394823096F1@quintile.net>
it is only done with filesystems, with other synthetic files we cannot seek.
http://git.9front.org/plan9front/plan9front/6617c63a374f7211b41252d3957e8a89061b8a49/commit.html
later it got changed to only apply to disk-filesystems, can't find
that commit right now
On 11/18/21, Steve Simon <steve@quintile.net> wrote:
>
> i am interested, where is the readahead? in cwfs, in the 9p kernel? in
> page(1)?
>
> -Steve
>
>
> On 18 Nov 2021, at 10:12 am, hiro <23hiro@gmail.com> wrote:
>
>
>>
>> However, when reading static files like pdfs and images (big filesize to
>> protocol ratio) it's really a benefit.
>>
>
> i doubt that, we have readahead, so unless you're bandwidth limited
> the 9p latency shouldn't matter. that is when the mountpoint that
> supplies the file is cwfs and it didn't get re-exported by something
> else...
>
next prev parent reply other threads:[~2021-11-18 23:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 22:39 sirjofri
2021-11-16 4:12 ` Xiao-Yong Jin
2021-11-16 18:18 ` Noam Preil
2021-11-16 19:04 ` Steve Simon
2021-11-17 1:51 ` hiro
2021-11-17 7:31 ` sirjofri
2021-11-17 9:45 ` hiro
2021-11-17 10:31 ` sirjofri
2021-11-17 15:31 ` hiro
2021-11-18 22:05 ` Steve Simon
2021-11-18 23:21 ` hiro [this message]
2021-11-17 21:35 ` sirjofri
2021-11-17 22:12 ` hiro
2021-11-17 22:52 ` Steve Simon
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=CAFSF3XOySmsf6z9pv+HAx8fVmTK+YXz_a2caZBNNosNZNn2Bsw@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).