From mboxrd@z Thu Jan 1 00:00:00 1970 From: ebiederm@xmission.com (Eric W. Biederman) Subject: Re: [PATCH 1/3] ftrace: add function tracing to single thread Date: Tue, 25 Nov 2008 22:23:16 -0800 Message-ID: References: <20081125223421.795046329@goodmis.org> <20081125223456.976670734@goodmis.org> <20081125144221.66eb99ad.akpm@linux-foundation.org> <20081125153104.ecdceed4.akpm@linux-foundation.org> <1227660839.12109.52.camel@nimitz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: In-Reply-To: (Steven Rostedt's message of "Wed, 26 Nov 2008 00:01:08 -0500 (EST)") Sender: linux-kernel-owner@vger.kernel.org To: Steven Rostedt Cc: Dave Hansen , Andrew Morton , containers@lists.osdl.org, fweisbec@gmail.com, Ingo Molnar , LKML , srostedt@redhat.com, Sukadev Bhattiprolu , "Serge E. Hallyn" List-Id: containers.vger.kernel.org Steven Rostedt writes: > On Tue, 25 Nov 2008, Eric W. Biederman wrote: > >> >> > > I'm speechless too. I'm a bit tired so probably am pushing to hard. At the same time I don't see a single reason not to use struct pid for what it was designed for. Identifying tasks. pid_t's really only belong at the border. I can see in the tracer when grabbing numbers you might not be able to follow pointers. For that I see justification for using task->pid. For the comparison I just don't see it. Eric