9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Anyone working on new upas/fs?
Date: Fri,  9 Feb 2007 10:42:33 -0500	[thread overview]
Message-ID: <ee9e417a0702090742y69a29d2fne2e93ea4479e051f@mail.gmail.com> (raw)
In-Reply-To: <e2aed9088c04fcb06a6af9e17253d876@coraid.com>

> I've got some heartburn about upas/fs.  Seems our
> user base is growing larger than main memories of our
> imap servers.  Anyone have any ideas to keep systems from
> running out of memory?  Anyone using something that
> virtual memory to keep the mail boxes?

Plan9ports has a new upas/fs (called mailfs for now,
and in $PLAN9/src/cmd/upas/nfs) with only an IMAP
back end, but it demand loads from the IMAP server.
I structured it so that it should not be hard to add a
module for reading local mailboxes too; those could
be loaded on demand as well.  Also, the existence of
the on-demand loading means one can treat memory
as a cache, tossing out messages as memory fills
and reloading them as needed.  One could even keep
a local disk cache of message pieces instead of requerying
a remote mailbox.

The hard part of adding local mailbox support should be
finding your place when the mailbox has changed underfoot,
not any structural part of the fs.

Russ


  parent reply	other threads:[~2007-02-09 15:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-09 15:35 Brantley Coile
2007-02-09 15:38 ` Francisco J Ballesteros
2007-02-09 15:42 ` Russ Cox [this message]
2007-02-09 16:08   ` erik quanstrom
2007-02-09 16:25     ` Russ Cox
2007-02-09 16:30       ` erik quanstrom
2007-02-09 16:41         ` 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=ee9e417a0702090742y69a29d2fne2e93ea4479e051f@mail.gmail.com \
    --to=rsc@swtch.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).