public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@zip.com.au>
To: Lorenzo Allegrucci <lenstra@tiscalinet.it>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Huge console switching lags
Date: Tue, 02 Oct 2001 09:57:22 -0700	[thread overview]
Message-ID: <3BB9F1F2.B6873DFD@zip.com.au> (raw)
In-Reply-To: <3.0.6.32.20011002111131.02693d90@pop.tiscalinet.it>

Lorenzo Allegrucci wrote:
> 
> I've experienced huge (4/5 seconds) console switching lags with
> 2.4.10 running this [1], never seen before with any kernel.

In 2.4.10, the console switching code moved from interrupt context
into process context.  So if your system is taking a long time to
schedule processes (in this case, keventd) then yes, console
switching will take a long time.

> 2.4.10-ac2 is even worse, it can take up to 10/20 seconds and longer
> to switch from a console to another (CTRL+F1,F2 etc) while running
> the beast below:
> 
> [1]
> #!/bin/sh
> bomb(){bomb|bomb&};bomb
> 

The simple ones are always the best ones, aren't they?

-

  reply	other threads:[~2001-10-02 16:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-02  9:11 Huge console switching lags Lorenzo Allegrucci
2001-10-02 16:57 ` Andrew Morton [this message]
2001-10-02 17:12   ` James Simmons
2001-10-02 18:10   ` Ricky Beam
2001-10-02 18:22     ` Andrew Morton
2001-10-02 18:24     ` Alan Cox
2001-10-02 18:32       ` Ricky Beam
2001-10-02 18:43         ` Alan Cox
2001-10-02 18:50         ` James Simmons
2001-10-02 22:39           ` Alan Cox
2001-10-02 22:50             ` James Simmons
2001-10-02 22:57               ` Alan Cox
2001-10-02 23:13                 ` James Simmons
2001-10-03 10:19                 ` Benjamin Herrenschmidt
2001-10-03 16:58                   ` James Simmons
2001-10-03 17:27                     ` Paul Mundt
2001-10-04  7:41               ` Geert Uytterhoeven
2001-10-04 16:49                 ` James Simmons
2001-10-02 18:56     ` Chris Wedgwood

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=3BB9F1F2.B6873DFD@zip.com.au \
    --to=akpm@zip.com.au \
    --cc=lenstra@tiscalinet.it \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox