From: "Roberto E. Vargas Caballero" <k0ga@shike2.com>
To: 9front@9front.org
Subject: Re: [9front] Re: devfs performance
Date: Wed, 19 Jan 2022 08:51:49 +0100 [thread overview]
Message-ID: <YefDFYkEl197r0t6@simple-cc.org> (raw)
In-Reply-To: <CA+61k5-7+QdG3zaee5+cMuyqqymMsmy+7zTxG+y+Cg9xkE2OFw@mail.gmail.com>
Hi,
On Mon, Jan 17, 2022 at 04:27:51PM +0100, Martijn Heil wrote:
> In the meantime I've started writing an (experimental) patch for
> devfs, that should at least work for my use if I succeed. I'll gladly
> share it if I consider it anywhere near worthy, but considering my
> inexperience with this kernel development I have no expectations.
> Nonetheless I'll try my best.
>
> In case anyone is interested in the technical details;
> Block-interleaved I/O is handled by interio() at /sys/src/9/port/devfs:1134.
> This in turn synchronously calls the blocking io() located at
> /sys/src/9/port/devfs:1031 for each sequential block to read from the
> inner devices.
I have interleaving in my disk configuration, and I thought that
the access was done in parallel. I think we should take a deep look
to your patch because otherwise the interleaving configuration
does not make sense.
Regards,
prev parent reply other threads:[~2022-01-19 10:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-16 15:27 [9front] " Martijn Heil
2022-01-17 15:27 ` [9front] " Martijn Heil
2022-01-19 2:37 ` ori
2022-01-19 7:51 ` Roberto E. Vargas Caballero [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=YefDFYkEl197r0t6@simple-cc.org \
--to=k0ga@shike2.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).