Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S266805AbUJAXc5 (ORCPT ); Fri, 1 Oct 2004 19:32:57 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266837AbUJAXc5 (ORCPT ); Fri, 1 Oct 2004 19:32:57 -0400 Received: from omx2-ext.sgi.com ([192.48.171.19]:58504 "EHLO omx2.sgi.com") by vger.kernel.org with ESMTP id S266805AbUJAXc4 (ORCPT ); Fri, 1 Oct 2004 19:32:56 -0400 Date: Fri, 1 Oct 2004 16:30:30 -0700 (PDT) From: Christoph Lameter X-X-Sender: clameter@schroedinger.engr.sgi.com To: Roland McGrath cc: Ulrich Drepper , johnstul@us.ibm.com, Ulrich.Windl@rz.uni-regensburg.de, george@mvista.com, linux-kernel@vger.kernel.org, libc-alpha@sources.redhat.com Subject: Re: [RFC] Posix compliant behavior of CLOCK_PROCESS/THREAD_CPUTIME_ID In-Reply-To: <200410012157.i91LvlPj021414@magilla.sf.frob.com> Message-ID: References: <200410012157.i91LvlPj021414@magilla.sf.frob.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 687 Lines: 15 On Fri, 1 Oct 2004, Roland McGrath wrote: > I have been working on an alternate patch that implements more complete CPU > clock functionality. This includes access to other threads' and process' > times, potentially finer-grained information (based on sched_clock), and > timers. I will post this code when it's ready, hopefully soon. Umm... How would you do that in a posix compliant way? This information is already available via /proc - 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/