All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: "<::.. Teresa_II ..::>" <teresa@kvitka.net>
Cc: CK Mailinglist <ck@vds.kolivas.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ck] Linux Kernel cfs scheduler and xorg kbd
Date: Tue, 31 Jul 2007 16:27:13 +0200	[thread overview]
Message-ID: <20070731142713.GD22209@elte.hu> (raw)
In-Reply-To: <1185882179.26459.36.camel@xtower.fri>


* <::.. Teresa_II ..::> <teresa@kvitka.net> wrote:

> У пн, 2007-07-30 у 22:25 +0200, <::.. Teresa_II ..::> пише:
> 
> Ok, hier is small testing: I started gcc emerge. System load is 
> between 1.47 and 1.61 I use SMP enabled 2.6.22.1-cfs-v19.1 kernel on 
> ADM64 X2.
> 
> In gnome-terminal window i just type fast "d" and until i count 1,2 i 
> hold SHIFT, than i release SHIFT, count 1,2 and than press SHIFT 
> again. I cound 1,2,1,2,1,2 as i type "d" button. That's the string i 
> get:

hm, do you have CONFIG_NO_HZ=y? If yes, could you disable it? Plus can 
you see the same problem on v2.6.23-rc1 as well (if that kernel boots 
fine for you).

	Ingo

  reply	other threads:[~2007-07-31 14:27 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-30 20:25 Linux Kernel cfs scheduler and xorg kbd <::.. Teresa_II ..::>
2007-07-30 22:49 ` Michal Piotrowski
2007-08-01  6:48   ` Ingo Molnar
2007-08-01 11:31     ` Andi Kleen
2007-08-01 11:01       ` Rene Herman
2007-08-01 12:34         ` Indan Zupancic
2007-08-01 12:50           ` Rene Herman
2007-08-01 13:07             ` Indan Zupancic
2007-08-01 13:26               ` Rene Herman
2007-08-01 13:33               ` <:::.. TeresaII ..:::>
2007-08-01 13:58                 ` Rene Herman
2007-08-01 14:44                   ` <::.. Teresa_II ..::>
2007-08-01 15:00                     ` [ck] " Matthew Hawkins
2007-08-01 15:53                       ` <::.. Teresa_II ..::>
2007-08-02  7:11                         ` Sébastien Dugué
2007-08-02 12:22                           ` Rene Herman
2007-08-02 13:18                             ` Indan Zupancic
2007-08-01 15:06                   ` Indan Zupancic
2007-08-01 15:09                     ` Ingo Molnar
2007-08-01 15:13                       ` Rene Herman
2007-08-01 15:20                         ` Ingo Molnar
2007-08-01 15:19                           ` Rene Herman
2007-08-01 15:26                       ` Indan Zupancic
2007-08-06  7:12                         ` Ingo Molnar
2007-08-06 13:10                           ` Rene Herman
2007-08-06 15:19                             ` Indan Zupancic
2007-08-06 17:46                               ` Rene Herman
2007-08-06 18:26                                 ` OT: enabling Xcomposite [was: Linux Kernel cfs scheduler and xorg kbd] Indan Zupancic
2007-08-07  4:40                     ` Linux Kernel cfs scheduler and xorg kbd Kyle Moffett
2007-08-07  6:05                       ` Arjan van de Ven
2007-08-07 10:17                         ` Indan Zupancic
2007-08-07 13:15                         ` Rene Herman
2007-08-09 21:14                           ` Mark Lord
2007-07-31 11:18 ` [ck] " <::.. Teresa_II ..::>
2007-07-31 11:42 ` <::.. Teresa_II ..::>
2007-07-31 14:27   ` Ingo Molnar [this message]
2007-07-31 16:39     ` <::.. Teresa_II ..::>
2007-07-31 15:06 ` Rene Herman

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=20070731142713.GD22209@elte.hu \
    --to=mingo@elte.hu \
    --cc=ck@vds.kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=teresa@kvitka.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 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.