9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Dave Eckhardt <davide+p9@cs.cmu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] rfork(RFPROC) and ffork()
Date: Mon, 31 Oct 2005 16:31:14 -0500	[thread overview]
Message-ID: <9541.1130794274@piper.nectar.cs.cmu.edu> (raw)
In-Reply-To: <A3801F07-7768-44CC-8D4C-BB64018B7B96@orthanc.ca>

>> Heck, it could be as simple as "each message is 1 directory,
>> containing chunks stored one per file, named by integers, and the
>> original message is formed by cat'ing the chunks in numerical
>> order".

> This turns out to be a pessimization.

Of what?

One possible goal (not the only consideration) would be for
the N copies of a monster attachment received by your N
users to occupy space==1 instead of space==N.  Cyrus IMAP
does this in certain circumstances.  Fossil+Venti will do
it automatically, but only (at present) if the attachment
is aligned the same way in each user's mailbox, which it
frequently won't be...or if it's stored out of line in a
separate file, which would align it the same way for all N
users.

Maybe it's not worth worrying about.

Dave Eckhardt


  reply	other threads:[~2005-10-31 21:31 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-29 15:34 erik quanstrom
2005-10-29 19:11 ` William Josephson
2005-10-29 19:18 ` Russ Cox
2005-10-29 23:00   ` erik quanstrom
2005-10-29 23:24     ` Francisco J Ballesteros
2005-10-29 23:38     ` Russ Cox
2005-10-30  0:19       ` erik quanstrom
2005-10-30  1:07         ` Russ Cox
2005-10-30  1:15           ` Ronald G Minnich
2005-10-30  1:22             ` geoff
2005-10-30  1:58               ` jmk
2005-10-30  1:54           ` Dave Eckhardt
2005-10-30  2:24           ` erik quanstrom
2005-10-30  2:51             ` geoff
2005-10-30  1:10         ` geoff
2005-10-30  1:18           ` Paul Lalonde
2005-10-30  6:52             ` Skip Tavakkolian
2005-10-30 10:14             ` Francisco J Ballesteros
2005-10-30 15:17             ` Russ Cox
2005-10-30 23:00               ` Dave Eckhardt
2005-10-30 23:14                 ` George Michaelson
2005-10-31  2:15                 ` erik quanstrom
2005-10-31  2:33                   ` geoff
2005-10-31  3:23                   ` Skip Tavakkolian
2005-10-31  4:20                 ` Lyndon Nerenberg
2005-10-31 21:31                   ` Dave Eckhardt [this message]
2005-10-31  4:06             ` [9fans] Scaleable mail repositories Lyndon Nerenberg
2005-10-31 10:55               ` C H Forsyth
2005-10-31 12:32                 ` erik quanstrom
2005-11-01 19:56                   ` rog
2005-11-01 22:29                     ` Francisco J Ballesteros
2005-11-08 19:56                       ` rog
2005-11-08 23:22                         ` Joel Salomon
2005-11-09  0:51                         ` Caerwyn Jones
2005-11-09  0:55                           ` Russ Cox
2005-11-09  3:32                         ` erik quanstrom
2005-10-31 15:30                 ` jmk
2005-10-30  1:10       ` [9fans] rfork(RFPROC) and ffork() William Josephson
2005-10-31 14:48 ` Russ Cox

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=9541.1130794274@piper.nectar.cs.cmu.edu \
    --to=davide+p9@cs.cmu.edu \
    --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).