Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756576Ab0KKUgF (ORCPT ); Thu, 11 Nov 2010 15:36:05 -0500 Received: from mx1.redhat.com ([209.132.183.28]:46931 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1749667Ab0KKUgD (ORCPT ); Thu, 11 Nov 2010 15:36:03 -0500 Date: Thu, 11 Nov 2010 21:29:22 +0100 From: Oleg Nesterov To: Linus Torvalds Cc: Mike Galbraith , Peter Zijlstra , Mathieu Desnoyers , Ingo Molnar , LKML , Markus Trippelsdorf Subject: Re: [RFC/RFT PATCH v3] sched: automated per tty task groups Message-ID: <20101111202922.GB16282@redhat.com> References: <20101021105114.GA10216@Krystal> <1287660312.3488.103.camel@twins> <20101021162924.GA3225@redhat.com> <1288076838.11930.1.camel@marge.simson.net> <1288078144.7478.9.camel@marge.simson.net> <1289489200.11397.21.camel@maggy.simson.net> <1289502511.11397.36.camel@maggy.simson.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.18 (2008-05-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 721 Lines: 18 On 11/11, Linus Torvalds wrote: > > Well, it cuts both ways. Maybe your approach is simpler and avoids > overhead at scheduling time. And "tsk->signal" may not be reliable due > to races with exit etc, so it may well be that going through the > signal struct could end up being a source of nasty races. I didn't > look whether the scheduler already derefenced ->signal for some other > reason, for example. Just in case, starting from 2.6.35 tsk->signal is reliable. Oleg. -- 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/