public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nick Piggin <piggin@cyberone.com.au>
To: martin f krafft <madduck@madduck.net>
Cc: linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: scheduling problems in X with 2.6.0
Date: Fri, 09 Jan 2004 02:47:30 +1100	[thread overview]
Message-ID: <3FFD7B92.8090301@cyberone.com.au> (raw)
In-Reply-To: <20040108154109.GB29224@piper.madduck.net>



martin f krafft wrote:

>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?
>

Yeah, my interactivity stuff has to be applied after my SMP stuff,
so I had to give you both ;)

You'll want to run make oldconfig after patching, and you needn't say
yes to CONFIG_SCHED_SMT, although if you did it wouldn't hurt either,
it just wouldn't do anything.

Nick



  reply	other threads:[~2004-01-08 15:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-07 10:23 scheduling problems in X with 2.6.0 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
2004-01-08 15:47         ` Nick Piggin [this message]
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=3FFD7B92.8090301@cyberone.com.au \
    --to=piggin@cyberone.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=madduck@madduck.net \
    /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