From: Ralf Baechle <ralf@linux-mips.org>
To: kernel coder <lhrkernelcoder@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: How to improve performance of 2.6 kernel
Date: Mon, 17 Oct 2005 17:07:08 +0100 [thread overview]
Message-ID: <20051017160708.GA8613@linux-mips.org> (raw)
In-Reply-To: <f69849430510170429t2735ed0fo3caa862c1dfea83a@mail.gmail.com>
On Mon, Oct 17, 2005 at 04:29:44AM -0700, kernel coder wrote:
> I have just ported linux kernel 2.6.10 for MIPS4Kc-core board.Before
> porting 2.6 kernel ,2.4.20 was running on this board. When I took
> benchmarks for both the kernels for comparison, I found out that
> linux-2.4.20 was giving much better results than linux-2.6.10. The
> specs for the board are as follows:
>
> --------------------------------------------------------------
> 133MHz MIPS4kc
How many TLB entries does your 4Kc have? 2.6 is hitting the TLB harder
and system that have small TLBs tend to suffer from that at the bottom
line even though all the other benefits of 2.6.
It would be interesting to see lmbench numbers for the system configurations
you've tested. Lmbench is a well defined workload that's proven useful
in isolating such issues.
Thanks,
Ralf
prev parent reply other threads:[~2005-10-17 16:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-17 11:29 How to improve performance of 2.6 kernel kernel coder
2005-10-17 12:36 ` Stuart Longland
2005-10-17 15:19 ` Kevin D. Kissell
2005-10-17 15:19 ` Kevin D. Kissell
2005-10-17 16:38 ` Dan Malek
2005-10-17 16:38 ` Dan Malek
2005-10-19 5:55 ` Fwd: " kernel coder
2005-10-19 15:53 ` Ralf Baechle
2005-10-17 16:07 ` Ralf Baechle [this message]
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=20051017160708.GA8613@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=lhrkernelcoder@gmail.com \
--cc=linux-mips@linux-mips.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