Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754169AbYA1Fxp (ORCPT ); Mon, 28 Jan 2008 00:53:45 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750802AbYA1Fxi (ORCPT ); Mon, 28 Jan 2008 00:53:38 -0500 Received: from smtp2.linux-foundation.org ([207.189.120.14]:34922 "EHLO smtp2.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750777AbYA1Fxh (ORCPT ); Mon, 28 Jan 2008 00:53:37 -0500 Date: Sun, 27 Jan 2008 21:52:42 -0800 From: Andrew Morton To: Vinay Sridhar Cc: linux-kernel@vger.kernel.org, libc-alpha@sourceware.org, drepper@redhat.com, wli@holomorphy.com, sripathik@in.ibm.com, "Eric W. Biederman" , Pavel Emelyanov Subject: Re: [RFC] Per-thread getrusage Message-Id: <20080127215242.b873c341.akpm@linux-foundation.org> In-Reply-To: <1200558425.5992.17.camel@srivinay.in.ibm.com> References: <1200558425.5992.17.camel@srivinay.in.ibm.com> X-Mailer: Sylpheed 2.4.1 (GTK+ 2.8.17; x86_64-unknown-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1631 Lines: 37 On Thu, 17 Jan 2008 13:57:05 +0530 Vinay Sridhar wrote: > Hi All, > > Last year, there was discussion about per-thread getrusage by adding > RUSAGE_THREAD flag to getrusage(). Please refer to the thread > http://lkml.org/lkml/2007/4/4/308. Ulrich had suggested that we should > design a better user-space API. Specifically, we need a > pthread_getrusage interface in the thread library, which accepts > pthread_t, converts pthread_t into the corresponding tid and passes it > down to the syscall. > > There are two ways to implement this in the kernel: > 1) Introduce an additional parameter 'tid' to sys_getrusage() and put > code in glibc to handle getrusage() and pthread_getrusage() calls > correctly. > 2) Introduce a new system call to handle pthread_getrusage() and leave > sys_getrusage() untouched. > > We implemented the second idea above, simply because it avoids touching > any existing code. We have implemented a new syscall, thread_getrusage() > and we have exposed pthread_getrusage() API to applications. > > Could you please share your thoughts on this? Does the approach look > alright? The code is hardly complete. It is just a prototype that works > on IA32 at the moment. > > ... > > +asmlinkage long sys_thread_getrusage(int tid, struct rusage __user *ru); What happens if `tid' refers to a thread in a different pid namespace? -- 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/