From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <728aafe49c38f76663622f541315ed73@quanstro.net>
From: erik quanstrom <quanstro@quanstro.net>
Date: Tue,  8 Sep 2009 13:16:24 -0400
To: 9fans@9fans.net
In-Reply-To: <4AA68C13.7080400@0x6a.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Subject: Re: [9fans] Petabytes on a budget: JBODs + Linux + JFS
Topicbox-Message-UUID: 6ab4565c-ead5-11e9-9d60-3106f5b1d025

> I read the paper you wrote and I have some (probably naive) questions:
> The section #6 labeled "core improvements" seems to suggest that the
> fileserver is basically using the CPU/fileserver hybrid kernel (both
> major changes are quoted as coming from the CPU kernel).  Is this just a
> one-off adjustment made by yourself, or have these changes been made
> permanent?

it's not a hybrid kernel.  it is just a file server kernel.  of course
the same c library and whatnot are used.  so there are shared
bits, but not many.

it is a one-off thing.  i also run the same fileserver at home.
the source is on sources as contrib quanstro/fs.  i don't think
anybody else runs it.

> Also, about the coraid AoE unit: am I correct in assuming that it does
> some sort of RAID functionality, and then presents the resulting
> device(s) as an AoE device (and nothing more)?

exactly.

> Also, another probably dumb question: did the the fileserver machine use
> the AoE device as a kenfs volume or a fossil(+venti)?

s/did/does/.  the fileserver is running today.

the fileserver provides the network with regular 9p fileserver
with three attach points (main, dump, other) accessable via il/ip.
from a client's view of the 9p messages, fossil, fossil+venti and
ken's fs would be difficult to distinguish.

- erik