From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] stream alternative?
Date: Mon, 11 Apr 2011 06:38:53 -0400 [thread overview]
Message-ID: <7701de2dc841cea75d598f543d9c24f7@ladd.quanstro.net> (raw)
In-Reply-To: <77bc353d-543a-4c00-9239-3cac84b0e9e3@bl1g2000vbb.googlegroups.co>
> Also, in a previous question (http://groups.google.com/group/
> comp.os.plan9/browse_thread/thread/771294cf1d34c337) it was stated
> that streams are no longer used. So what's the present mechanism that
> replaces streams?
there isn't one. you can't dynamically reconfigure i/o paths in plan 9.
however, since everything's a file server, one can construct fairly
arbitrary chains of devices. (and given the bread/bwrite calls in the
kernel, it can be zero-copy.)
zB: aoe(3) presents basic block devices. partitions aren't supported.
however, sdaoe(3) which is a lightly specialized version of sdloop(3)
turns one into a sd(3) device, which does support partitions. sdloop
(only in 9atom) can do the same thing for anything that looks like a
regular file.
so imagine that i for some bizarre reason i wanted to run raid50
locally on aoe targets. i could run a fictive sdraid5 on a fictive
set of sdraid1 devices which in turn were built from sdaoe on top
of aoe. so you'd have
sdraid5* <-> sdraid1* <-> sdaoe <-> aoe <-> ether
maybe that looks like streams to you, even if it's not dynamically
reconfigurable.
personally, that looks more like Device in ken's file server
to me.
- erik
next parent reply other threads:[~2011-04-11 10:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <77bc353d-543a-4c00-9239-3cac84b0e9e3@bl1g2000vbb.googlegroups.co>
2011-04-11 10:38 ` erik quanstrom [this message]
2011-04-11 9:19 faif
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=7701de2dc841cea75d598f543d9c24f7@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--cc=9fans@9fans.net \
/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).