From: martin f krafft <madduck@madduck.net>
To: Nick Piggin <piggin@cyberone.com.au>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: scheduling problems in X with 2.6.0
Date: Thu, 8 Jan 2004 16:41:09 +0100 [thread overview]
Message-ID: <20040108154109.GB29224@piper.madduck.net> (raw)
In-Reply-To: <3FFD789D.7020908@cyberone.com.au>
[-- Attachment #1: Type: text/plain, Size: 970 bytes --]
also sprach Nick Piggin <piggin@cyberone.com.au> [2004.01.08.1634 +0100]:
> You could try my alternate CPU scheduler which would tell us if your
> problem is the scheduler or something else. Its against the mm tree.
> http://www.kerneltrap.org/~npiggin/v29p6.gz
From a quick glance, it mentions the Pentium 4 and Hyperthreading.
This *is* an SMP system, but it uses Athlon XPs. Will your scheduler
still work?
--
martin; (greetings from the heart of the sun.)
\____ echo mailto: !#^."<*>"|tr "<*> mailto:" net@madduck
invalid/expired pgp subkeys? use subkeys.pgp.net as keyserver!
government announcement - the government announced today that it is
changing its mascot to a condom because it more clearly reflects the
government's political stance. a condom stands up to inflation, halts
production, destroys the next generation, protects a bunch of pricks
and finally, gives you a sense of security while you're being screwed!
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2004-01-08 15:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-07 10:23 martin f krafft
2004-01-07 15:30 ` Nick Piggin
2004-01-07 17:46 ` martin f krafft
2004-01-08 15:34 ` Nick Piggin
2004-01-08 15:41 ` martin f krafft [this message]
2004-01-08 15:47 ` Nick Piggin
2004-01-08 15:42 ` martin f krafft
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=20040108154109.GB29224@piper.madduck.net \
--to=madduck@madduck.net \
--cc=linux-kernel@vger.kernel.org \
--cc=piggin@cyberone.com.au \
/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®