From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751357AbWFBJZZ (ORCPT ); Fri, 2 Jun 2006 05:25:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751358AbWFBJZZ (ORCPT ); Fri, 2 Jun 2006 05:25:25 -0400 Received: from mail03.syd.optusnet.com.au ([211.29.132.184]:53391 "EHLO mail03.syd.optusnet.com.au") by vger.kernel.org with ESMTP id S1751357AbWFBJZY (ORCPT ); Fri, 2 Jun 2006 05:25:24 -0400 From: Con Kolivas To: "Chen, Kenneth W" Subject: Re: [PATCH RFC] smt nice introduces significant lock contention Date: Fri, 2 Jun 2006 19:25:05 +1000 User-Agent: KMail/1.9.1 Cc: "'Nick Piggin'" , linux-kernel@vger.kernel.org, "'Chris Mason'" , "Ingo Molnar" References: <000001c68625$614f59a0$0c4ce984@amr.corp.intel.com> In-Reply-To: <000001c68625$614f59a0$0c4ce984@amr.corp.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200606021925.06089.kernel@kolivas.org> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org On Friday 02 June 2006 19:17, Chen, Kenneth W wrote: > What about the part in dependent_sleeper() being so bully and actively > resched other low priority sibling tasks? I think it would be better > to just let the tasks running on sibling CPU to finish its current time > slice and then let the backoff logic to kick in. That would defeat the purpose of smt nice if the higher priority task starts after the lower priority task is running on its sibling cpu. -- -ck