All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Mason <mason@suse.com>
To: Hans Reiser <reiser@namesys.com>
Cc: Oleg Drokin <green@namesys.com>, Steve Pratt <slpratt@us.ibm.com>,
	reiserfs-list@namesys.com
Subject: Re: Problems with journal size option on mkfs
Date: 16 May 2002 09:02:41 -0400	[thread overview]
Message-ID: <1021554161.16587.776.camel@tiny> (raw)
In-Reply-To: <3CE39F5D.6010604@namesys.com>

On Thu, 2002-05-16 at 08:00, Hans Reiser wrote:
>
> Yes, I admit I was thinking as I pressed send about just how much stuff 
> would be going into pre1 and wondering if it should be broken into pre1, 
> pre2, and pre3.
> 
> Probably the journal relocation stuff, being the most tested in 2.5 (do 
> any reiserfs users use it in 2.5 though?), should go into pre3.
> 
> The bitmap code and the file write code should go into pre1, along with 
> the cleanups.
> 
> Feel free to suggest different orderings, though maybe we should only 
> think about this when it is time for it....

I think we should start with the speedups only.  Lets get the bitmap
code in 2.5.x (ASAP, I'm willing to merge if Oleg is busy) and the file
write changes seem to have a little ways to go.

I believe the relocation stuff should be tested in andrea's and/or
Alan's kernels before we submit for 2.4.21preX.  We shouldn't mix
must-have speedups with nice to have features (as large as the
relocation anyway) in the same 2.4.x series.

-chris



  reply	other threads:[~2002-05-16 13:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-15 20:12 Problems with journal size option on mkfs Steve Pratt
2002-05-16  5:16 ` Oleg Drokin
2002-05-16 10:47   ` Hans Reiser
2002-05-16 11:00     ` Yury Umanets
2002-05-16 10:55       ` Hans Reiser
2002-05-16 11:52     ` Chris Mason
2002-05-16 12:00       ` Hans Reiser
2002-05-16 13:02         ` Chris Mason [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-05-15 21:49 Steve Pratt
2002-05-15 23:43 ` Chris Mason
2002-05-16 14:59 Steve Pratt
2002-05-16 15:09 ` Oleg Drokin
2002-05-16 15:15   ` Hans Reiser
2002-05-16 16:14     ` Edward Shushkin

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=1021554161.16587.776.camel@tiny \
    --to=mason@suse.com \
    --cc=green@namesys.com \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@namesys.com \
    --cc=slpratt@us.ibm.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.