Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1761507AbZATOZd (ORCPT ); Tue, 20 Jan 2009 09:25:33 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1755019AbZATOZZ (ORCPT ); Tue, 20 Jan 2009 09:25:25 -0500 Received: from mailhub.sw.ru ([195.214.232.25]:2501 "EHLO relay.sw.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753696AbZATOZY (ORCPT ); Tue, 20 Jan 2009 09:25:24 -0500 From: Vitaliy Gusev To: Oleg Nesterov Subject: Re: [PATCH] kthread: Don't looking for a task in create_kthread() #2 Date: Tue, 20 Jan 2009 17:16:34 +0300 User-Agent: KMail/1.9.6 (enterprise 20070904.708012) Cc: Andrew Morton , Christoph Hellwig , linux-kernel@vger.kernel.org, Pavel Emelyanov References: <200901201345.42054.vgusev@openvz.org> <20090120120642.GA9497@redhat.com> In-Reply-To: <20090120120642.GA9497@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200901201716.34842.vgusev@openvz.org> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 940 Lines: 34 On 20 January 2009 15:06:42 Oleg Nesterov wrote: > On 01/20, Vitaliy Gusev wrote: > > > > Remove the unnecessary find_task_by_pid_ns(). kthread() can just > > use "current" to get the same result. > > I think the patch is nice and correct. > > > > BTW. Perhaps it also makes sense to move sched_setscheduler/etc code > from create_kthread() to kthread_create(), what do you think? I don't thinks so. create_kthread() is executed in kthreadd process and sched_setscheduler/etc preparation things are reflected to kthreadd's CPU usage. In other words it is a kthreadd matter, start and setup a thread. > > (of course, this needs another patch) > > Oleg. > > -- Thank, Vitaliy Gusev -- 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/