9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Uriel <uriel99@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] kenfs (look ma, no disks)
Date: Sun,  9 Sep 2007 18:09:01 +0200	[thread overview]
Message-ID: <5d375e920709090909h5c405abdsa5130eddbf793dfa@mail.gmail.com> (raw)
In-Reply-To: <e29f8c89781c04f3ba474a56487b004c@quanstro.net>

Any chance this could live in sources? Even if kenfs is not part of
the distribution anymore, it would be nice to have 'unofficial' place
where people who still want it can find the latest version.

uriel

On 9/9/07, erik quanstrom <quanstro@quanstro.net> wrote:
> i've been working on kenfs as we needed a way to have
> automatic offsite backup.  i am using aoe to do the offsite
> bit so theoretically, one could have a kenfs with no disks.
> i've also rewritten the marvell sata driver, added the intel
> ahci driver, revamped mmu code.  finally, i have a slight
> change to the on-disk layout of the c part of the cw that
> results in a 20x speed improvement.  (this change can be
> used on old fses if you dump and then recover using
> the new code.)  i've also implemented a new compile-time
> option "fastworm" that inhibits copying from the worm to
> the cache.
>
> my current testing setup is
>
>         filsys main cp(a0)0.10{a1e99.0[e64.<0-3>]}
>
> where
>
>         dev     driver  target
>         a?      ahci
>         e99.0   aoe     sr421
>         e64.?   aoe     pata shelf accessed over wireless link.
>
> if you have any interest in this, please drop me a note
> with the hardware you're using and i'll figure out how
> to arrange access.
>
> - erik
>
>


  reply	other threads:[~2007-09-09 16:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-09 16:03 erik quanstrom
2007-09-09 16:09 ` Uriel [this message]
2007-09-09 16:21   ` erik quanstrom

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=5d375e920709090909h5c405abdsa5130eddbf793dfa@mail.gmail.com \
    --to=uriel99@gmail.com \
    --cc=9fans@cse.psu.edu \
    /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).