Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 2 Oct 2001 14:55:21 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 2 Oct 2001 14:55:10 -0400 Received: from weta.f00f.org ([203.167.249.89]:20886 "EHLO weta.f00f.org") by vger.kernel.org with ESMTP id ; Tue, 2 Oct 2001 14:55:01 -0400 Date: Wed, 3 Oct 2001 06:56:11 +1200 From: Chris Wedgwood To: Ricky Beam Cc: Andrew Morton , Lorenzo Allegrucci , linux-kernel@vger.kernel.org Subject: Re: Huge console switching lags Message-ID: <20011003065611.B28891@weta.f00f.org> In-Reply-To: <3BB9F1F2.B6873DFD@zip.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.20i X-No-Archive: Yes Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/