Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755237AbXJISPK (ORCPT ); Tue, 9 Oct 2007 14:15:10 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754271AbXJISO6 (ORCPT ); Tue, 9 Oct 2007 14:14:58 -0400 Received: from ms-smtp-02.nyroc.rr.com ([24.24.2.56]:37042 "EHLO ms-smtp-02.nyroc.rr.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752137AbXJISO5 (ORCPT ); Tue, 9 Oct 2007 14:14:57 -0400 Date: Tue, 9 Oct 2007 14:14:31 -0400 (EDT) From: Steven Rostedt X-X-Sender: rostedt@gandalf.stny.rr.com To: Gregory Haskins cc: Peter Zijlstra , Ingo Molnar , linux-rt-users , kravetz@us.ibm.com, LKML , pmorreale@novell.com, sdietrich@novell.com Subject: Re: [RFC PATCH RT] push waiting rt tasks to cpus with lower prios. In-Reply-To: <1191952777.23198.8.camel@localhost.localdomain> Message-ID: References: <20071009142044.4941.65189.stgit@novell1.haskins.net> <1191944024.4281.72.camel@ghaskins-t60p.haskins.net> <1191952777.23198.8.camel@localhost.localdomain> 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: 25 -- On Tue, 9 Oct 2007, Steven Rostedt wrote: > This has been complied tested (and no more ;-) > > > The idea here is when we find a situation that we just scheduled in an > RT task and we either pushed a lesser RT task away or more than one RT > task was scheduled on this CPU before scheduling occurred. > > The answer that this patch does is to do a O(n) search of CPUs for the > CPU with the lowest prio task running. When that CPU is found the next > highest RT task is pushed to that CPU. I don't want that O(n) to scare anyone. It really is a O(1) but with a K = NR_CPUS. I was saying if you grow the NR_CPUS the search grows too. -- Steve - 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/