From: Andrew Morton <akpm@linux-foundation.org>
To: Pavel Emelyanov <xemul@openvz.org>
Cc: Vinay Sridhar <vinay@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, libc-alpha@sourceware.org,
drepper@redhat.com, wli@holomorphy.com, sripathik@in.ibm.com,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [RFC] Per-thread getrusage
Date: Mon, 28 Jan 2008 01:10:10 -0800 [thread overview]
Message-ID: <20080128011010.d162d336.akpm@linux-foundation.org> (raw)
In-Reply-To: <479D88C7.5030101@openvz.org>
On Mon, 28 Jan 2008 10:48:23 +0300 Pavel Emelyanov <xemul@openvz.org> wrote:
> Andrew Morton wrote:
> > On Thu, 17 Jan 2008 13:57:05 +0530 Vinay Sridhar <vinay@linux.vnet.ibm.com> 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?
> >
>
> That's impossible. I explicitly deny namespace creation in case the
> CLONE_THREAD is specified. So all threads of a single process always
> live in one pid namespace.
>
If the code was using find_task_by_vpid() then OK (I guess). But it is
looking the tids up in the init_pid_ns. Which I assume means that if it's
in a new namespace and is looking up a sibling thread it will simply fail?
Or am I missing something?
next prev parent reply other threads:[~2008-01-28 9:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-17 8:27 [RFC] Per-thread getrusage Vinay Sridhar
2008-01-17 15:42 ` Ulrich Drepper
2008-01-19 1:14 ` Roland McGrath
2008-01-19 1:14 ` [PATCH] RUSAGE_THREAD Roland McGrath
2008-01-19 6:21 ` Ulrich Drepper
2008-01-21 9:55 ` Christoph Hellwig
2008-01-26 7:23 ` Michael Kerrisk
2008-01-28 5:52 ` [RFC] Per-thread getrusage Andrew Morton
2008-01-28 7:48 ` Pavel Emelyanov
2008-01-28 9:10 ` Andrew Morton [this message]
2008-01-28 9:38 ` Pavel Emelyanov
2008-01-28 9:45 ` Andrew Morton
2008-01-28 9:57 ` Pavel Emelyanov
2008-01-28 20:43 ` Eric W. Biederman
2008-01-28 21:57 ` Andrew Morton
2008-01-29 8:17 ` Pavel Emelyanov
2008-01-29 8:29 ` Pavel Emelyanov
2008-01-28 8:24 ` Sripathi Kodi
2008-01-28 9:22 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080128011010.d162d336.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=drepper@redhat.com \
--cc=ebiederm@xmission.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sripathik@in.ibm.com \
--cc=vinay@linux.vnet.ibm.com \
--cc=wli@holomorphy.com \
--cc=xemul@openvz.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox