From: Andrew Morton <akpm@digeo.com>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>,
Con Kolivas <conman@kolivas.net>
Subject: Re: [PATCHSET] Linux 2.4.20-jam0
Date: Fri, 29 Nov 2002 16:47:50 -0800 [thread overview]
Message-ID: <3DE80AB6.611F3A8C@digeo.com> (raw)
In-Reply-To: 20021129233807.GA1610@werewolf.able.es
"J.A. Magallon" wrote:
>
> - Orlov inode allocator for 2.4
The Orlov allocator in 2.5 has caused a tremendous performance regression
in dbench-on-ext3/ordered-on-scsi.
I don't know why yet - I doubt if it's due to the allocator itself - more
likely an IO scheduling bug in ext3, or a bug in the 2.5 elevator.
There is no such regression on IDE - presumably write caching is covering
up the problem.
So that's something to watch out for.
(where did your Orlov patch from? All the tabs are mangled)
You'll need to port this missing bit, which provides the `oldalloc'
and `orlov' mount options.
fs/ext3/super.c | 4 ++++
1 files changed, 4 insertions(+)
--- 25/fs/ext3/super.c~ext3-oldalloc Fri Nov 29 02:21:20 2002
+++ 25-akpm/fs/ext3/super.c Fri Nov 29 02:22:03 2002
@@ -662,6 +662,10 @@ static int parse_options (char * options
return 0;
sbi->s_resuid = v;
}
+ else if (!strcmp (this_char, "oldalloc"))
+ set_opt (sbi->s_mount_opt, OLDALLOC);
+ else if (!strcmp (this_char, "orlov"))
+ clear_opt (sbi->s_mount_opt, OLDALLOC);
#ifdef CONFIG_JBD_DEBUG
else if (!strcmp (this_char, "ro-after")) {
unsigned long v;
_
next prev parent reply other threads:[~2002-11-30 0:40 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-29 23:38 [PATCHSET] Linux 2.4.20-jam0 J.A. Magallon
2002-11-30 0:47 ` Andrew Morton [this message]
2002-11-30 14:45 ` J.A. Magallon
2002-11-30 14:58 ` Sean Neakums
2002-11-30 15:02 ` J.A. Magallon
2002-11-30 22:15 ` Andrew Morton
2002-11-30 6:36 ` hugang
2002-11-30 14:58 ` J.A. Magallon
2002-11-30 17:07 ` Mike Galbraith
2002-11-30 17:50 ` Andrea Arcangeli
2002-11-30 23:36 ` J.A. Magallon
2002-12-01 1:55 ` J.A. Magallon
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=3DE80AB6.611F3A8C@digeo.com \
--to=akpm@digeo.com \
--cc=conman@kolivas.net \
--cc=jamagallon@able.es \
--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