From owner-cvs-src@FreeBSD.ORG Wed Mar 1 16:45:02 2006 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5C14816A420; Wed, 1 Mar 2006 16:45:02 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id ADB3F43D72; Wed, 1 Mar 2006 16:45:00 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k21GiuuO063390; Wed, 1 Mar 2006 09:44:56 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <4405CF88.4040904@samsco.org> Date: Wed, 01 Mar 2006 09:44:56 -0700 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Andrew Gallatin References: <200602282224.k1SMOtJt070241@repoman.freebsd.org> <200602281735.12240.jhb@freebsd.org> <4404D37E.9040502@samsco.org> <20060301113803.A8330@grasshopper.cs.duke.edu> In-Reply-To: <20060301113803.A8330@grasshopper.cs.duke.edu> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: cvs-src@FreeBSD.org, src-committers@FreeBSD.org, cvs-all@FreeBSD.org, John Baldwin Subject: Re: cvs commit: src/sys/amd64/amd64 intr_machdep.c io_apic.c local_apic.c mp_machdep.c src/sys/amd64/include apicvar.h intr_machdep.h src/sys/amd64/isa atpic.c src/sys/i386/i386 intr_machdep.c io_apic.c local_apic.c mp_machdep.c ... X-BeenThere: cvs-src@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the src tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2006 16:45:02 -0000 Andrew Gallatin wrote: > Scott Long [scottl@samsco.org] wrote: > <...> > >> Also, it's not so >>much important which CPU gets the interrupt as it is which CPU runs the >>ithread for that interrupt. I guess that you can get a little better >>latency by preempting directly from the low-level interrupt handler into >>the ithread, but I don't know if that is noticable noise above the cost >>of the context switch and inevitable lock operations and contention >>involved. > > > What do you mean by "preempting directly from the low-level interrupt > handler into the ithread" ? Do you mean running the ithread directly > in the context of the hardware interrupt until it does something where > it needed to block? Do we do this now? > > Thanks, > > Drew > > No, I just mean that the CPU running the low-level handler is likely to schedule and run the ithread as soon as the interrupt exits, preempting whatever thread happened to be running before the interrupt occurred. This isn't context stealing, it's just preferential scheduling. You still need to wind through the scheduler and do a context switch to get there. Scott