Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754519Ab0LTKqw (ORCPT ); Mon, 20 Dec 2010 05:46:52 -0500 Received: from mailout-de.gmx.net ([213.165.64.23]:54345 "HELO mail.gmx.net" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with SMTP id S1753009Ab0LTKqv (ORCPT ); Mon, 20 Dec 2010 05:46:51 -0500 X-Authenticated: #14349625 X-Provags-ID: V01U2FsdGVkX187BelajFk7PeLrlirQN0wHRnars6lZys7Nm+fCpm Cny8hnq/wYHVC2 Subject: Re: [RFC -v2 PATCH 2/3] sched: add yield_to function From: Mike Galbraith To: Avi Kivity Cc: Rik van Riel , kvm@vger.kernel.org, linux-kernel@vger.kernel.org, Srivatsa Vaddagiri , Peter Zijlstra , Chris Wright In-Reply-To: <4D0F3266.90908@redhat.com> References: <20101213224434.7495edb2@annuminas.surriel.com> <20101213224657.7e141746@annuminas.surriel.com> <1292306896.7448.157.camel@marge.simson.net> <4D0A6D34.6070806@redhat.com> <1292569018.7772.75.camel@marge.simson.net> <4D0B7D24.5060207@redhat.com> <1292615509.7381.81.camel@marge.simson.net> <4D0CE937.8090601@redhat.com> <1292699204.1181.51.camel@marge.simson.net> <4D0DA45A.9070600@redhat.com> <1292753156.16367.104.camel@marge.simson.net> <4D0DCE10.7000200@redhat.com> <1292834372.8948.27.camel@marge.simson.net> <4D0F1794.3010803@redhat.com> <1292835302.8948.35.camel@marge.simson.net> <4D0F1BD8.20601@redhat.com> <1292837440.8948.60.camel@marge.simson.net> <4D0F25E8.80305@redhat.com> <1292841193.11946.36.camel@marge.simson.net> <4D0F3266.90908@redhat.com> Content-Type: text/plain; charset="UTF-8" Date: Mon, 20 Dec 2010 11:46:50 +0100 Message-ID: <1292842010.11946.39.camel@marge.simson.net> Mime-Version: 1.0 X-Mailer: Evolution 2.30.1.2 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1243 Lines: 34 On Mon, 2010-12-20 at 12:39 +0200, Avi Kivity wrote: > On 12/20/2010 12:33 PM, Mike Galbraith wrote: > > > > > > Correct. I don't want the other task to run before me, I just don't > > > want to run before it. > > > > OK, so what I gather is that if you can preempt another of your own > > threads to get the target to cpu, that would be a good thing whether > > he's on the same cpu as yield_to() caller or not. If the target is > > sharing a cpu with you, that's even better. Correct? > > Correct. I'm not interested in scheduling wrt other tasks, just my tasks. > > However, if I'm all alone on my cpu, and the other task is runnable but > not running, behind some unrelated task, then I do need that task to be > preempted (or to move tasks around). So in that case, a pull may be advantageous. > > Would a kick/hint option be useful? > > Depends on what it does... Let you decide whether you only want to drop a hint and leave it at that, or also attempt a preemption. -Mike -- 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/