Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752989Ab2BVBG3 (ORCPT ); Tue, 21 Feb 2012 20:06:29 -0500 Received: from mail-pz0-f46.google.com ([209.85.210.46]:61044 "EHLO mail-pz0-f46.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752020Ab2BVBG2 (ORCPT ); Tue, 21 Feb 2012 20:06:28 -0500 Authentication-Results: mr.google.com; spf=pass (google.com: domain of htejun@gmail.com designates 10.68.190.8 as permitted sender) smtp.mail=htejun@gmail.com; dkim=pass header.i=htejun@gmail.com Date: Tue, 21 Feb 2012 17:06:23 -0800 From: Tejun Heo To: Frederic Weisbecker Cc: Mandeep Singh Baines , "Paul E. McKenney" , Li Zefan , LKML , Oleg Nesterov , Andrew Morton Subject: Re: [PATCH 2/2] cgroup: Walk task list under tasklist_lock in cgroup_enable_task_cg_list Message-ID: <20120222010623.GJ12236@google.com> References: <1328668647-24125-1-git-send-email-fweisbec@gmail.com> <1328668647-24125-3-git-send-email-fweisbec@gmail.com> <20120221222343.GU3090@google.com> <20120222005525.GC13403@somewhere.redhat.com> <20120222010015.GH12236@google.com> <20120222010431.GD13403@somewhere.redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20120222010431.GD13403@somewhere.redhat.com> User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 743 Lines: 20 On Wed, Feb 22, 2012 at 02:04:34AM +0100, Frederic Weisbecker wrote: > > Guys, this is one time thing. It happens *once* after boot and we're > > already holding exclusive lock. There's no reason to optimize this at > > all. Let's just keep it simple. > > For now I agree. But one day the real time guys might eye that thing. If the latency issue ever comes up, I think the right thing to do is just disable the lazy optimization. ie. Just chain tasks from the beginning. Thanks. -- tejun -- 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/