All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shawn Rutledge <shawn.t.rutledge@gmail.com>
To: Hans Reiser <reiser@namesys.com>
Cc: "Vladimir V. Saveliev" <vs@namesys.com>, reiserfs-list@namesys.com
Subject: Re: where is the journal kept?
Date: Tue, 16 Aug 2005 13:27:25 -0700	[thread overview]
Message-ID: <d9a6586e05081613275071c00a@mail.gmail.com> (raw)
In-Reply-To: <4302458E.9070604@namesys.com>

On 8/16/05, Hans Reiser <reiser@namesys.com> wrote:
> Reiser4 does a very nice job of packing the tree tightly, which is
> independent of seeks.  Ditto for compression plugin.
> He merely needs to ignore some code, he is not harmed by it.  If he
> wants to write a new block allocator, sure, why not, we have allocator
> plugins yes?   His will just be simpler.....

But the most important thing is to reduce the number of writes as low
as possible.

  reply	other threads:[~2005-08-16 20:27 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-15 11:53 where is the journal kept? Payal Rathod
2005-08-15 12:25 ` Vladimir V. Saveliev
2005-08-15 12:50   ` Payal Rathod
2005-08-15 12:58     ` Vladimir V. Saveliev
2005-08-15 13:12       ` Pat Double
2005-08-15 14:26         ` Vladimir V. Saveliev
2005-08-15 15:52           ` David Masover
2005-08-15 16:19           ` Shawn Rutledge
2005-08-15 17:34             ` Vladimir V. Saveliev
2005-08-15 18:08               ` Shawn Rutledge
2005-08-16 19:59                 ` Hans Reiser
2005-08-16 20:27                   ` Shawn Rutledge [this message]
2005-08-16 22:30                     ` David Masover
2005-08-16 23:23                       ` Shawn Rutledge
2005-08-17  0:02                         ` David Masover
2005-08-17  0:47                           ` Shawn Rutledge
2005-08-17  5:51                       ` Hans Reiser

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=d9a6586e05081613275071c00a@mail.gmail.com \
    --to=shawn.t.rutledge@gmail.com \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=vs@namesys.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.