From: Ookhoi <ookhoi@humilis.net>
To: Voicu Liviu <liviu.voicu@huji.ac.il>
Cc: ookhoi@humilis.net, reiserfs-list@namesys.com
Subject: Re: ReiserFS causes CPU high usage?!
Date: Fri, 28 Feb 2003 14:33:55 +0100 [thread overview]
Message-ID: <20030228143354.M24291@humilis> (raw)
In-Reply-To: <200302281533.02318.liviu.voicu@huji.ac.il>
Voicu Liviu wrote (ao):
> > > This is my .config file of the kernel 2.4.20..,maybe you can find some
> > > wrong in here..........
> > >
> > > # CONFIG_MPENTIUMIII is not set
> > > # CONFIG_MPENTIUMIII31 is not set
> > > # CONFIG_MPENTIUM4 is not set
> > > CONFIG_MPENTIUM431=y
> >
> > What cpu is this? This is not in a 2.4.20 kernel. Are you sure this is
> > the right .config?
> > You should use CONFIG_MPENTIUM4 I think.
>
> i have applyed 13_gcc31-compile-optimizations patch
> (this gives me specific march for the cpu i want)
>
> +ifdef CONFIG_MPENTIUM431
> +CFLAGS += -march=pentium4 -mmmx -msse -msse2 -falign-functions=4
> - -fprefetch-loop-arrays -maccumulate-outgoing-args
> +endif
>
> see?
Jup, ok.
> > > CONFIG_BLK_DEV_IDEDISK=y
> > > CONFIG_IDEDISK_MULTI_MODE=y
> >
> > Why this one?
>
> well, not sure about these...these are my patches........
>
> # ls
> 001_o1_pe_ll_021215_ck_2.4.20.patch.bz2
> 005_supermount_021215_ck_2.4.20.patch.bz2
> 010_tune_021217_ck_2.4.20.patch.bz2
> 002_aavm_021215_ck_2.4.20.patch.bz2 007_acpi_021215_ck_2.4.20.patch.bz2
> 011_vt_021217_ck_2.4.20.patch.bz2
> 003_rl2_021215_ck.2.4.20.patch.bz2 008_vh_021217_ck_2.4.20.patch.bz2
Ok, now please try again with the latest 2.4.21-preX
next prev parent reply other threads:[~2003-02-28 13:33 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-27 22:11 ReiserFS causes CPU high usage?! Voicu Liviu
2003-02-28 7:51 ` Oleg Drokin
2003-02-28 12:03 ` Voicu Liviu
2003-02-28 12:24 ` Ookhoi
2003-02-28 12:35 ` Voicu Liviu
2003-02-28 12:35 ` Ookhoi
2003-02-28 12:39 ` Voicu Liviu
2003-02-28 12:38 ` Ookhoi
2003-02-28 12:42 ` Voicu Liviu
2003-02-28 12:45 ` Ookhoi
2003-02-28 12:54 ` Voicu Liviu
2003-02-28 13:00 ` Ookhoi
2003-02-28 13:04 ` Voicu Liviu
2003-02-28 13:13 ` Voicu Liviu
2003-02-28 13:26 ` Ookhoi
2003-02-28 13:33 ` Voicu Liviu
2003-02-28 13:33 ` Ookhoi [this message]
2003-02-28 13:45 ` Voicu Liviu
2003-02-28 13:48 ` Ookhoi
2003-02-28 13:52 ` Voicu Liviu
2003-02-28 14:02 ` Oleg Drokin
2003-02-28 14:08 ` Voicu Liviu
2003-02-28 12:48 ` Voicu Liviu
2003-02-28 12:56 ` Hans Reiser
2003-02-28 12:57 ` Ookhoi
2003-02-28 13:01 ` Voicu Liviu
2003-02-28 13:37 ` Manuel Krause
2003-02-28 12:56 ` Ookhoi
2003-02-28 13:00 ` Voicu Liviu
2003-02-28 13:06 ` Ookhoi
2003-02-28 13:11 ` Voicu Liviu
2003-02-28 13:13 ` Ookhoi
2003-02-28 13:19 ` Voicu Liviu
2003-02-28 13:32 ` Ookhoi
2003-02-28 13:36 ` Voicu Liviu
2003-02-28 13:33 ` Hans Reiser
2003-02-28 13:39 ` Voicu Liviu
2003-02-28 14:07 ` Oleg Drokin
2003-02-28 14:12 ` Voicu Liviu
2003-02-28 14:16 ` Oleg Drokin
2003-02-28 13:10 ` Dieter Nützel
2003-02-28 14:57 ` John Dalbec
2003-02-28 16:43 ` Jeff Mahoney
2003-03-01 15:40 ` Vladimir Karavelov
2003-03-01 18:03 ` Voicu Liviu
2003-02-28 12:07 ` Hans Reiser
2003-02-28 12:11 ` Voicu Liviu
2003-02-28 12:13 ` Marc-Christian Petersen
2003-02-28 12:19 ` Voicu Liviu
2003-02-28 12:23 ` Szabolcs Szasz
2003-02-28 12:56 ` Voicu Liviu
2003-02-28 13:02 ` Szabolcs Szasz
2003-02-28 12:25 ` Toby Dickenson
2003-02-28 12:34 ` Voicu Liviu
2003-02-28 12:34 ` Marc-Christian Petersen
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=20030228143354.M24291@humilis \
--to=ookhoi@humilis.net \
--cc=liviu.voicu@huji.ac.il \
--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.