From: "Charles Heselton" <charles-heselton@cox.net>
To: "Dieter Nützel" <Dieter.Nuetzel@hamburg.de>,
"Dan Mann" <mainlylinux@attbi.com>
Cc: "Linux Kernel List" <linux-kernel@vger.kernel.org>
Subject: RE: Kernel 2.5.6 Interactive performance
Date: Sat, 9 Mar 2002 17:00:15 -0800 [thread overview]
Message-ID: <NFBBKFIFGLNJKLMMGGFPOEPCCFAA.charles-heselton@cox.net> (raw)
In-Reply-To: <200203092055.57348.Dieter.Nuetzel@hamburg.de>
How would you implement these thing? I'm not on the same technical level
that you guys are, and when/if things are out of context, I don't follow.
Can you help?
Charles Heselton
Network Installer
Staffing Alternatives, Inc.
619.261.6866
charles_heselton@hotmail.com <mailto:charles_heselton@hotmail.com>
-----Original Message-----
From: linux-kernel-owner@vger.kernel.org
[mailto:linux-kernel-owner@vger.kernel.org]On Behalf Of Dieter Nützel
Sent: Saturday, March 09, 2002 1156
To: Dan Mann
Cc: Linux Kernel List
Subject: Re: Kernel 2.5.6 Interactive performance
On Saturday, 9. März 2002 18:55:00, Dan Mann wrote:
[-]
>Machine now feels more responsive than windows 2000 pro machine at work.
>
> Great work guys.
It's due to preemption and Ingo's great O(1)-scheduler.
BIO should help, too but throughput isn't were it should be...;-)
You can get this when you apply preemption+lock-break, O(1) and Andrew
Morten's low-latency to 2.4.18, too.
-aa (vm_29) deliver additional throughput.
If you are running under KDE you should try 3.0 beta2 or -rc2 (!!!)
It flies then.
Regards,
Dieter
--
Dieter Nützel
Graduate Student, Computer Science
University of Hamburg
Department of Computer Science
@home: Dieter.Nuetzel@hamburg.de
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2002-03-10 1:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-09 19:55 Dieter Nützel
2002-03-10 1:00 ` Charles Heselton [this message]
2002-03-10 1:11 ` Dieter Nützel
2002-03-10 1:15 ` Charles Heselton
2002-03-10 4:23 ` Robert Love
2002-03-10 4:38 ` Mike Fedyk
2002-03-10 4:55 ` J Sloan
2002-03-10 6:05 ` Robert Love
2002-03-10 6:18 ` Charles Heselton
2002-03-11 1:05 ` Andrea Arcangeli
[not found] <003301c1c7fd$a67d08f0$bb187143@amer.cisco.com>
2002-03-10 7:23 ` Charles Heselton
-- strict thread matches above, loose matches on Subject: below --
2002-03-08 0:14 2.5.6-3 -- preempt_schedule unresolved in snd-pcm.o, snd-emu10k1-synth.o and snd-emu10k1.o Miles Lane
2002-03-09 18:55 ` Kernel 2.5.6 Interactive performance Dan Mann
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=NFBBKFIFGLNJKLMMGGFPOEPCCFAA.charles-heselton@cox.net \
--to=charles-heselton@cox.net \
--cc=Dieter.Nuetzel@hamburg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mainlylinux@attbi.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®