9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: weigelt@metux.de, 9fans@9fans.net
Subject: Re: [9fans] Ideas for gc on venti
Date: Wed, 18 Jun 2008 16:32:47 -0400	[thread overview]
Message-ID: <3919c08679c5ef8fc6d801c62acfbc3b@quanstro.net> (raw)
In-Reply-To: <20080618193533.GA23589@nibiru.local>

> Well, that's not yet any form of gc - just an smooth data moving
> from one volume to another - also good if you intend to take some
> disk offline in near future, w/o serious interruption.
> (The deprecated volume get emptier and emptier, and no new
> data is added.)

in the original venti paper, the problems associated with disk
management, redundancy and backup were ignored so they
could be handled seperately.

i think this is good design.  but i can't take credit for this
opinion.  i've had kernighan & plauger, elements of programming
style on my desk for a few days.  this is a book old enough to give
examples in pl/1 but i think it still gives advice which bears repeating.

one of the suggestions is that each function should hide something
important.

it makes sense for the storage managment function to present an
idealized block device while hiding details like disk replacement
and redundency.

now, if i could get all my own functions to live up to this standard....

- erik




  parent reply	other threads:[~2008-06-18 20:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-18 19:35 Enrico Weigelt
2008-06-18 20:16 ` Russ Cox
2008-06-18 20:50   ` Enrico Weigelt
2008-06-18 20:32 ` erik quanstrom [this message]
     [not found] ` <d39497d76feddcee629a4ea8c7af63d9@quanstro.net>
2008-06-18 20:57   ` Enrico Weigelt
2008-06-18 21:29     ` Bakul Shah
2008-06-18 22:37       ` Skip Tavakkolian
2008-06-18 22:54         ` erik quanstrom
2008-06-19 12:46     ` erik quanstrom
2008-06-19 14:20       ` a
2008-06-19 14:33         ` 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=3919c08679c5ef8fc6d801c62acfbc3b@quanstro.net \
    --to=quanstro@quanstro.net \
    --cc=9fans@9fans.net \
    --cc=weigelt@metux.de \
    /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).