From: Pat Double <pat@patdouble.com>
To: David Masover <ninja@slaphack.com>
Cc: reiserfs-list@namesys.com
Subject: Re: reiser4 performance
Date: Tue, 9 Aug 2005 21:49:51 -0500 [thread overview]
Message-ID: <200508092149.51707.pat@patdouble.com> (raw)
In-Reply-To: <42F96737.7050809@slaphack.com>
On Tuesday 09 August 2005 09:32 pm, David Masover wrote:
> Pat Double wrote:
> > Actually I did make it public, hit the wrong command on my mail client ;)
> >
> > I did not try the -mm kernel (latest patches is for -mm5 IIRC), I use
> > software suspend 2 and it does not apply to the 2.6.12.x-mm series.
> > Except for this problem reiser4 has worked great for me. Since I use a
> > single partition and '/' does not get modified much I copied all my data
> > over, rebuilt the filesystem, and then started using it. I have not
> > discovered any problems, and the filesystem is quite fast.
>
> That's with the mm reiser4, or the reiser4-for-2.6?
>
> Glad to hear it works with Suspend2. That's going to be the next thing
> I try, once my system is back up to speed. I'm on Gentoo, so
> understandably it takes awhile to get back up to speed, Godlike amd64
> speeds notwithstanding.
I used the reiser4-for-2.6 patches. Before the 2.6.12 patches were available I
tried the -mm patches from reiser4-for-2.6 which applied cleanly. When 2.6.12
recently I tried those with the same results. I did not try the -mm kernel
sources because even if they worked flawlessly it would be no help to me.
Suspend 2 is more important to me than reiser4. Shutdown in 30 seconds,
startup in 30 seconds is more useful to me.
--
Pat Double, pat@patdouble.com
"In the beginning God created the heaven and the earth."
next prev parent reply other threads:[~2005-08-10 2:49 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-08 10:32 reiser4 performance Hemiplegic Menehune
2005-08-08 10:51 ` PFC
2005-08-08 11:09 ` Raymond A. Meijer
2005-08-08 13:38 ` Ingo Bormuth
2005-08-08 16:44 ` PFC
2005-08-08 19:53 ` David Masover
2005-08-08 20:30 ` michael chang
2005-08-08 20:34 ` michael chang
2005-08-08 20:40 ` Bedros Hanounik
2005-08-08 20:58 ` michael chang
2005-08-08 21:41 ` Ingo Bormuth
2005-08-08 20:51 ` Funding [Was:reiser4 performance] Pysiak Satriani
2005-08-08 19:56 ` reiser4 performance David Masover
2005-08-08 22:06 ` Hans Reiser
2005-08-09 0:02 ` David Masover
2005-08-09 0:16 ` michael chang
2005-08-09 1:02 ` David Masover
2005-08-09 17:52 ` michael chang
2005-08-09 20:19 ` Valdis.Kletnieks
2005-08-10 1:23 ` David Masover
2005-08-10 21:33 ` Hans Reiser
2005-08-08 18:09 ` Hans Reiser
2005-08-08 18:10 ` Hans Reiser
2005-08-08 23:13 ` Gregory Maxwell
2005-08-08 23:30 ` Hans Reiser
2005-08-09 0:20 ` David Masover
2005-08-09 0:58 ` Gregory Maxwell
2005-08-09 1:33 ` David Masover
2005-08-09 1:55 ` Gregory Maxwell
2005-08-11 18:49 ` Hans Reiser
2005-08-11 19:00 ` PFC
2005-08-11 21:29 ` Gregory Maxwell
2005-08-09 2:03 ` Gregory Maxwell
2005-08-10 1:34 ` David Masover
2005-08-10 1:51 ` Pat Double
2005-08-10 2:11 ` David Masover
2005-08-10 2:19 ` Pat Double
2005-08-10 2:32 ` David Masover
2005-08-10 2:49 ` Pat Double [this message]
2005-08-09 7:41 ` PFC
-- strict thread matches above, loose matches on Subject: below --
2005-08-08 20:57 Pysiak Satriani
2005-08-08 22:42 ` 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=200508092149.51707.pat@patdouble.com \
--to=pat@patdouble.com \
--cc=ninja@slaphack.com \
--cc=reiserfs-list@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.