From owner-svn-src-all@FreeBSD.ORG Sat Jul 24 20:02:46 2010 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 28A4D1065677 for ; Sat, 24 Jul 2010 20:02:46 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id DF9DF8FC15 for ; Sat, 24 Jul 2010 20:02:45 +0000 (UTC) Received: (qmail 30815 invoked by uid 399); 24 Jul 2010 20:02:44 -0000 Received: from localhost (HELO laptop.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 24 Jul 2010 20:02:44 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Date: Sat, 24 Jul 2010 13:02:43 -0700 (PDT) From: Doug Barton To: Alexander Motin In-Reply-To: <4C4B4231.80406@FreeBSD.org> Message-ID: References: <201007241049.o6OAnxvo001874@svn.freebsd.org> <4C4B4231.80406@FreeBSD.org> User-Agent: Alpine 2.00 (BSF 1167 2008-08-23) X-message-flag: Outlook -- Not just for spreading viruses anymore! OpenPGP: id=1A1ABC84 Organization: http://SupersetSolutions.com/ MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: svn commit: r210444 - head/sys/x86/x86 X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 24 Jul 2010 20:02:46 -0000 On Sat, 24 Jul 2010, Alexander Motin wrote: > Doug Barton wrote: >> On Sat, 24 Jul 2010, Alexander Motin wrote: >>> Author: mav >>> Date: Sat Jul 24 10:49:59 2010 >>> New Revision: 210444 >>> URL: http://svn.freebsd.org/changeset/base/210444 >>> >>> Log: >>> Increment td->td_intr_nesting_level for LAPIC timer interrupts. Among >>> other >>> things it hints SCHED_ULE to run clock swi handlers on their native >>> CPUs, >>> avoiding many unneeded IPI_PREEMPT calls. >> >> Will this help SCHED_4BSD at all? I'm finding it to be slightly better >> for interactivity on a loaded system, but frankly at this point they >> both leave a lot to be desired. > > At least not directly. SCHED_4BSD doesn't use this variable. But I have > no idea if the problem exist there. Even on SCHED_ULE it happens only in > some cases, if swi thread was accidentally pushed out of it's CPU by > higher priority thread. 4BSD has different migration logic, so behavior > could be different there. Ok, thanks. Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso