From owner-cvs-src@FreeBSD.ORG Fri Jan 26 22:55:36 2007 Return-Path: X-Original-To: cvs-src@FreeBSD.org Delivered-To: cvs-src@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 02EDB16A403; Fri, 26 Jan 2007 22:55:36 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.freebsd.org (Postfix) with ESMTP id BAB4B13C48A; Fri, 26 Jan 2007 22:55:35 +0000 (UTC) (envelope-from bright@elvis.mu.org) Received: by elvis.mu.org (Postfix, from userid 1192) id 9D2981A4D84; Fri, 26 Jan 2007 14:55:35 -0800 (PST) Date: Fri, 26 Jan 2007 14:55:35 -0800 From: Alfred Perlstein To: Jeff Roberson Message-ID: <20070126225535.GX56065@elvis.mu.org> References: <200701252352.l0PNq0I4074466@repoman.freebsd.org> <20070125183242.T564@10.0.0.1> <20070126223437.GW56065@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20070126223437.GW56065@elvis.mu.org> User-Agent: Mutt/1.4.2.2i Cc: cvs-src@FreeBSD.org, Jeff Roberson , src-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/kern sched_ule.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: Fri, 26 Jan 2007 22:55:36 -0000 * Alfred Perlstein [070126 14:34] wrote: > * Jeff Roberson [070125 19:47] wrote: > > > > On Thu, 25 Jan 2007, Jeff Roberson wrote: > > > > >jeff 2007-01-25 23:52:00 UTC > > > > > > FreeBSD src repository > > > > > > Modified files: > > > sys/kern sched_ule.c > > > Log: > > > - Implement much more intelligent ipi sending. This algorithm tries to > > > minimize IPIs and rescheduling when scheduling like tasks while keeping > > > latency low for important threads. > > Forgot: Will IPI when: > > > > > 1) An idle thread is running. > > > 2) The current thread is worse than realtime and the new thread is > > > better than realtime. Realtime to realtime doesn't preempt. > > > 3) The new thread's priority is less than the threshold. > > Out of curiosity, have you tried a polling mode where the idlethread > will check a word each iteration an in effect pull a soft IPI? > > I'm not sure this would help or hinder, but it is of interest to me. (for everyone else) as per discussion on IRC, it doesn't seem to be useful to do so because a busy system will rarely actually run the idlethread. -- - Alfred Perlstein, RED Incorporated Consulting. - coder / sysadmin / FreeBSD Hacker / All that jazz -