From: Chris Wedgwood <cw@f00f.org>
To: Ricky Beam <jfbeam@bluetopia.net>
Cc: Andrew Morton <akpm@zip.com.au>,
Lorenzo Allegrucci <lenstra@tiscalinet.it>,
linux-kernel@vger.kernel.org
Subject: Re: Huge console switching lags
Date: Wed, 3 Oct 2001 06:56:11 +1200 [thread overview]
Message-ID: <20011003065611.B28891@weta.f00f.org> (raw)
In-Reply-To: <3BB9F1F2.B6873DFD@zip.com.au> <Pine.GSO.4.33.0110021408310.22872-100000@sweetums.bluetronic.net>
In-Reply-To: <Pine.GSO.4.33.0110021408310.22872-100000@sweetums.bluetronic.net>
On Tue, Oct 02, 2001 at 02:10:41PM -0400, Ricky Beam wrote:
And what's the brilliant reason for this? And don't give any BS
about it taking too long inside an interrupt context -- we're
switching consoles not start netscrape.
Having console switching in interrupt context was horrible... I would
much rather have the 'odd' slightly delayed console switch than drop
stuff or have sound jitter every time I switch console (which sucks
badly).
Under even fairly heavy load here it's not a problem, what problems
does the new bahaviour create (sorry, a fork bomb is a silly
example). With a load-average of over 20 its still responsive.
--cw
prev parent reply other threads:[~2001-10-02 18:55 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
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 [this message]
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=20011003065611.B28891@weta.f00f.org \
--to=cw@f00f.org \
--cc=akpm@zip.com.au \
--cc=jfbeam@bluetopia.net \
--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