Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 2 Oct 2001 14:32:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 2 Oct 2001 14:32:00 -0400 Received: from sweetums.bluetronic.net ([66.57.88.6]:38142 "EHLO sweetums.bluetronic.net") by vger.kernel.org with ESMTP id ; Tue, 2 Oct 2001 14:31:50 -0400 Date: Tue, 2 Oct 2001 14:32:08 -0400 (EDT) From: Ricky Beam X-X-Sender: To: Alan Cox cc: Andrew Morton , Lorenzo Allegrucci , Subject: Re: Huge console switching lags In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Tue, 2 Oct 2001, Alan Cox wrote: >A console switch has to wait until queued I/O to that console is complete, Ok, so fix that. (assuming that's not "waiting on the hardware" queued IO) >Also a console switch on a frame buffer with no hardware banking can take >a lot of time. Oh, *grin*, forgot about those evil framebuffer consoles. (never use them myself, they really are freakin' slow.) Arguablly, all access to fbdev's should be from a process context (it's like having X in the kernel.) In that case, keventd needs to be a high priority real-time task. If it takes SECONDS to change consoles, I'm very likely to assume the machine is locked and push the reset button (and I'm sure many others will do the same.) --Ricky - 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/