public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Hans Reiser <reiser@bitshadow.namesys.com>
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org
Subject: Re: [BK] [PATCH] reiserfs changeset 7 of 7 to include into 2.4 tree
Date: Fri, 09 Aug 2002 13:52:24 -0700	[thread overview]
Message-ID: <3D542B88.6F7007E4@zip.com.au> (raw)
In-Reply-To: 200208091636.g79GadA9007889@bitshadow.namesys.com

Hans Reiser wrote:
> 
> Hello!
> 
>    This changeset implements new block allocator for reiserfs and adds one
>    more tail policy. This is a product of continuous NAMESYS research in this
>    area. This piece of code incorporates work by Alexander Zarochencev,
>    Jeff Mahoney and Oleg Drokin.

What Christoph said ;)

Block allocation algorithms are really, really important.  I'd be very interested
in a description of what this change does, what problems it is solving, how it
solves them, observed results, testing methodology, etc.   Is such a thing
available?

Thanks.

  parent reply	other threads:[~2002-08-09 20:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-09 16:36 [BK] [PATCH] reiserfs changeset 7 of 7 to include into 2.4 tree Hans Reiser
2002-08-09 17:38 ` Christoph Hellwig
2002-08-11 20:21   ` Alan Cox
2002-08-11 20:18     ` Hans Reiser
2002-08-11 20:40       ` Hans Reiser
2002-08-09 20:52 ` Andrew Morton [this message]
2002-08-10 17:55   ` Hans Reiser
2002-08-10 18:14   ` Hans Reiser
2002-08-12 18:36     ` Marcelo Tosatti
2002-08-12 20:01       ` Hans Reiser
2002-08-12 20:33       ` 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=3D542B88.6F7007E4@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcelo@conectiva.com.br \
    --cc=reiser@bitshadow.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox