From: Ole-Hjalmar Kristensen <ole.hjalmar.kristensen@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] two ventis?
Date: Wed, 13 Dec 2017 08:41:38 +0100 [thread overview]
Message-ID: <CAHqDL__D_pWmqkAmYn4Xybjsz210d5LpcGONVTuzAiUVdeRueQ@mail.gmail.com> (raw)
In-Reply-To: <7FFDD24C-832A-487E-92F0-ED8AA54C6097@quintile.net>
[-- Attachment #1: Type: text/plain, Size: 1305 bytes --]
I imagine that you would get problems with duplicates. You could duplicate
enough of the caches and internal structures that it would work, but then
you would be close to having two instances of venti anyway. But maybe, if
you removed the assumption that there are no duplicates, and changed venti
to just index the first instance of a score/value pair.
On Wed, Dec 13, 2017 at 1:08 AM, Steve Simon <steve@quintile.net> wrote:
> true
>
> i have my old work archives and rather than merge that venti into my main
> one i could just mount it via vacfs on demand (from 9fs). but can one venti
> cope with two incompatible sets of arenas?
>
> -Steve
>
>
> On 12 Dec 2017, at 21:58, Ole-Hjalmar Kristensen <
> ole.hjalmar.kristensen@gmail.com> wrote:
>
> Strictly speaking, isn't venti just content-addressable block storage, not
> a file system? Anyway, I'm curious to know what you are going to use this
> for.
>
> On Tue, Dec 12, 2017 at 9:41 PM, Steve Simon <steve@quintile.net> wrote:
>
>> Can a venti instance be configured to service to two seperate venti
>> filesystems? They would need different names and different listner
>> names but can they share a process / buffer cache?
>>
>> I guess the alternative is to run two seperate instances.
>>
>> -Steve
>>
>>
>
[-- Attachment #2: Type: text/html, Size: 2278 bytes --]
prev parent reply other threads:[~2017-12-13 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 20:41 Steve Simon
2017-12-12 21:58 ` Ole-Hjalmar Kristensen
2017-12-13 0:08 ` Steve Simon
2017-12-13 7:41 ` Ole-Hjalmar Kristensen [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=CAHqDL__D_pWmqkAmYn4Xybjsz210d5LpcGONVTuzAiUVdeRueQ@mail.gmail.com \
--to=ole.hjalmar.kristensen@gmail.com \
--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).