Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752449AbaAXK2U (ORCPT ); Fri, 24 Jan 2014 05:28:20 -0500 Received: from tango.0pointer.de ([85.214.72.216]:46976 "EHLO tango.0pointer.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752419AbaAXK2Q (ORCPT ); Fri, 24 Jan 2014 05:28:16 -0500 X-Greylist: delayed 452 seconds by postgrey-1.27 at vger.kernel.org; Fri, 24 Jan 2014 05:28:16 EST Date: Fri, 24 Jan 2014 11:20:38 +0100 From: Lennart Poettering To: Peter Zijlstra Cc: Dan Ballard , kay.sievers@vrfy.org, Rob Landley , Andrew Morton , Minto Joseph , Cyrill Gorcunov , Pavel Emelyanov , Naoya Horiguchi , Rik van Riel , Frederic Weisbecker , Thomas Gleixner , Mel Gorman , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH 1/1] add StartTimeMonotomic, StartTimeBootTime to per pid in /proc Message-ID: <20140124102037.GE4870@tango.0pointer.de> References: <20140122155351.GV13532@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20140122155351.GV13532@twins.programming.kicks-ass.net> Organization: Red Hat, Inc. X-Campaign-1: () ASCII Ribbon Campaign X-Campaign-2: / Against HTML Email & vCards - Against Microsoft Attachments User-Agent: Leviathan/19.8.0 [zh] (Cray 3; I; Solaris 4.711; Console) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 22.01.14 16:53, Peter Zijlstra (peterz@infradead.org) wrote: > > On Tue, Jan 21, 2014 at 07:10:04AM -0800, Dan Ballard wrote: > > starttime in /proc/$PID/stat is inaccurate by "clock tick" granularity. > > The kernel keeps better track os this exposes that in /prod/$PID/status > > as StartTimeMonotonic and StartTimeBootTime > > Why? Well, the canonical way to expose clocks to userspace these days is with CLOCK_MONOTONIC, CLOCK_BOOTTIME, and so on. The starttime is currently exposed in a way that is made inaccurate by the clock tick in /proc/$PID/stat. Dan's patch simply unfucks that interface. The process starttime is useful for a variety of things, like figuring out creation ordering of processes. Or it is useful to detect PID reuses in a somewhat reliable way. It is useful information to show the admin in "ps". Profilers like "bootchart" can use this information to plot when precisely specific process got started. From the outside it is often useful to see for how long a specific process has already been running, for accounting needs, and so on. Note that Dan's patch doesn't add any new timestamp logic to the kernel, it just exposes the existing timestamps in a way to userspace that is more in line with the rest of timestamps exposed. Lennart -- 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/