Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261566AbVEYVFj (ORCPT ); Wed, 25 May 2005 17:05:39 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261567AbVEYVFi (ORCPT ); Wed, 25 May 2005 17:05:38 -0400 Received: from lirs02.phys.au.dk ([130.225.28.43]:54918 "EHLO lirs02.phys.au.dk") by vger.kernel.org with ESMTP id S261566AbVEYVFZ (ORCPT ); Wed, 25 May 2005 17:05:25 -0400 Date: Wed, 25 May 2005 23:05:05 +0200 (METDST) From: Esben Nielsen To: Tom Vier Cc: Daniel Walker , linux-kernel@vger.kernel.org Subject: Re: RT patch acceptance In-Reply-To: <20050525205841.GB28913@zero> 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 Content-Length: 895 Lines: 21 On Wed, 25 May 2005, Tom Vier wrote: > If irqs are run in threads, which are scheduled, how are they scheduled? > fifo? What's the point then; simply to let the top half run to completion > before another top half starts? If it's about setting scheduling priorities > for irq threads, some one top half can prempt another, why not just use irq > levels, like bsd (using pic's is slower than using threads?)? > Long interrupt handlers can be interrupt by _tasks_, not only other interrupts! An audio application running in userspace can be scheduled over an ethernet interrupt handler copying data from the controller into RAM (without DMA). Esben - 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/