From: Ralf Baechle <ralf@linux-mips.org>
To: kernel coder <lhrkernelcoder@gmail.com>
Cc: linux-mips@linux-mips.org
Subject: Re: Fwd: How to improve performance of 2.6 kernel
Date: Wed, 19 Oct 2005 16:53:57 +0100 [thread overview]
Message-ID: <20051019155357.GH2616@linux-mips.org> (raw)
In-Reply-To: <f69849430510182255m59d62726h7a4b9c96e1a7f07c@mail.gmail.com>
On Wed, Oct 19, 2005 at 10:55:01AM +0500, kernel coder wrote:
> I did lmbench benchmarks tests... and the results i got were pretty
> weird.. I am attaching the jpegs :) of the graphs i made in MS Excel.
We're happy with cold, raw ASCII numbers :)
> Btw, I have implemented NAPI in both 2.4.20 and 2.6.10. I ported the
> code to linux-2.6 in order to increase the board's efficiency but I'm
> quite dissapointed with the results so far :(.
NAPI is doing it's job which is keeping a system responsive under extreme
loads very well. The pre-NAPI behaviour was simply locking up thus making
systems easily DOS-able. NAPI is not meant to improve latency; it isn't
meant but frequently mistaken to.
Ralf
next prev parent reply other threads:[~2005-10-19 15:54 UTC|newest]
Thread overview: 12+ 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 [this message]
2005-10-17 16:07 ` Ralf Baechle
-- strict thread matches above, loose matches on Subject: below --
2005-10-19 18:12 Fwd: " Mitchell, Earl
2005-10-19 18:12 ` Mitchell, Earl
2005-10-20 9:36 ` Ralf Baechle
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=20051019155357.GH2616@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 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.