From: Ed Sweetman <ed.sweetman@wmich.edu>
To: Alex Tomas <bzzz@tmi.comex.ru>
Cc: linux-kernel@vger.kernel.org, ext2-devel@lists.sourceforge.net
Subject: Re: [RFC] extents support for EXT3
Date: Fri, 29 Aug 2003 11:52:05 -0400 [thread overview]
Message-ID: <3F4F76A5.6020000@wmich.edu> (raw)
In-Reply-To: <m3vfsgpj8b.fsf@bzzz.home.net>
Alex Tomas wrote:
>>>>>>Ed Sweetman (ES) writes:
>
>
> ES> If it's the same as test2 then i've already tried it. I got no
> ES> performance gains as far as dbench is concerned. Perhaps my block
> ES> size is not optimal on that partition for extents. Either way it
> ES> seemed to make the kernel unstable and i've been trying to fix things
> ES> since mid-day yesterday. Been getting very strange problems, no error
> ES> messages are reported or anything like that.
>
> I still use -test2, because -test4 detects my scsi hdds in another order
> than -test2. last time I sent rediff against -test4. what kind of problem
> did you see?
>
in the kernels that would boot (for some reason test4's videodev driver
is borked so i used the mm patchset) passed the serio drivers, init was
unable to be found, no matter what even though it mounted the root fs
and the root fs is not as far as i can tell when booting on older
kernels, corrupted. I'm writing now in mozilla from the very system
but with extents turned off. I'm somewhat afraid though that even
though i didn't mount the partitions with the extents option, that the
patch may still be having an adverse effect. Right now things seem
pretty stable but last night apt was hanging while generating locales
reproducably causing the entire kernel to lose the ability to do
anything to the fs. This was all being tested on test3-mm1. I am aware
that mm does have some patches to ext3 that aren't in the main kernel i
believe. perhaps the xattr stuff is conflicting in some way? I really
have no way of testing the linus tree directly because the drivers i use
wont compile.
All in all though, when it was enabled, i saw really no difference from
when it was not enabled. dbench 16 gave me ~140MB/sec either way.
md5summing large files resulted in equal performance as well. I got
nothing even close to the kind of performance increases you showed in
the first mail.
next prev parent reply other threads:[~2003-08-29 15:52 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 8:22 [RFC] extents support for EXT3 Alex Tomas
2003-08-28 17:22 ` [Ext2-devel] " Mike Fedyk
2003-08-29 5:55 ` Alex Tomas
2003-08-28 18:12 ` Ed Sweetman
2003-08-29 5:59 ` Alex Tomas
2003-08-29 15:28 ` Ed Sweetman
2003-08-29 15:38 ` Alex Tomas
2003-08-29 15:52 ` Ed Sweetman [this message]
2003-08-29 16:10 ` Alex Tomas
2003-08-29 16:16 ` Alex Tomas
2003-08-29 16:20 ` Ed Sweetman
2003-08-29 16:34 ` Alex Tomas
2003-08-29 17:49 ` Ed Sweetman
2003-08-29 18:09 ` Alex Tomas
2003-08-29 19:55 ` Ed Sweetman
2003-08-29 21:39 ` [Ext2-devel] " Mike Fedyk
2003-08-29 22:25 ` Ed Sweetman
2003-08-29 23:17 ` Mike Fedyk
2003-08-31 20:25 ` Eric W. Biederman
2003-08-31 20:37 ` Alex Tomas
2003-09-05 10:06 ` Pavel Machek
2003-09-05 14:55 ` Eric W. Biederman
2003-08-30 9:09 ` Alex Tomas
2003-08-30 8:55 ` Alex Tomas
2003-08-30 10:13 ` Alex Tomas
2003-08-28 22:00 ` Ramón Rey Vicente
2003-08-29 6:04 ` Alex Tomas
2003-08-29 9:55 ` Ramón Rey Vicente
2003-09-06 0:19 ` jw schultz
2003-09-06 6:09 ` Alex Tomas
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=3F4F76A5.6020000@wmich.edu \
--to=ed.sweetman@wmich.edu \
--cc=bzzz@tmi.comex.ru \
--cc=ext2-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
/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