Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Fri, 6 Jul 2001 15:25:40 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Fri, 6 Jul 2001 15:25:30 -0400 Received: from perninha.conectiva.com.br ([200.250.58.156]:29957 "HELO perninha.conectiva.com.br") by vger.kernel.org with SMTP id ; Fri, 6 Jul 2001 15:25:10 -0400 Date: Fri, 6 Jul 2001 16:24:52 -0300 (BRST) From: Rik van Riel X-X-Sender: To: Sasha Pachev Cc: Mike Kravetz , Subject: Re: Strange thread behaviour on 8-way x86 machine In-Reply-To: <0107061245200U.17811@mysql> 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 On Fri, 6 Jul 2001, Sasha Pachev wrote: > Upon further investigation and testing, it turned out that the kernel was not > at fault - the problem was high mutex contention, which caused frequent > context switches, and the idle CPU was apparently from the scheduler waiting > for the original CPU to become available too often. > > On a side note, it would be nice if a process could communicate > to the kernel that it would rather run on the first available > CPU than wait for the perfect one to become available. The kernel already does this. Rik -- Executive summary of a recent Microsoft press release: "we are concerned about the GNU General Public License (GPL)" http://www.surriel.com/ http://www.conectiva.com/ http://distro.conectiva.com/ - 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/