From: Dan Ballard <dan@mindstab.net>
To: Peter Zijlstra <peterz@infradead.org>,
kay.sievers@vrfy.org, Rob Landley <rob@landley.net>,
Andrew Morton <akpm@linux-foundation.org>,
Minto Joseph <mvaliyav@redhat.com>,
Cyrill Gorcunov <gorcunov@openvz.org>,
Pavel Emelyanov <xemul@parallels.com>,
Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>,
Rik van Riel <riel@redhat.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Mel Gorman <mgorman@suse.de>,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] add StartTimeMonotomic, StartTimeBootTime to per pid in /proc
Date: Fri, 31 Jan 2014 07:42:40 -0800 [thread overview]
Message-ID: <d7f132a9ede3ce67d74f899a66cdaf86@mindstab.net> (raw)
In-Reply-To: <20140124113203.GZ30183@twins.programming.kicks-ass.net>
>> 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.
>
> OK, maybe. Changelog should have said so.
>
> Yeah, Dan was also too lazy to explain the need, and had like 3 typoes
> in the inadequate changelog he had.
>
> Does not inspire confidence.
>
> Now please all untwist your panties and try and submit a proper patch.
Resubmitted with more explanation (and less typos). If you feel that
having
both CLOCK_MONOTONIC and CLOCK_BOOTTIME is really a sticking point I'd
be
ok to remove one as long as the other made it through, as one is much
better
than none.
prev parent reply other threads:[~2014-01-31 15:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-21 15:10 [PATCH 1/1] add StartTimeMonotomic, StartTimeBootTime to per pid in /proc Dan Ballard
2014-01-22 15:53 ` Peter Zijlstra
2014-01-23 14:52 ` Dan Ballard
2014-01-23 15:20 ` Peter Zijlstra
2014-01-24 10:20 ` Lennart Poettering
2014-01-24 11:32 ` Peter Zijlstra
2014-01-24 12:49 ` Lennart Poettering
2014-01-31 15:42 ` Dan Ballard [this message]
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=d7f132a9ede3ce67d74f899a66cdaf86@mindstab.net \
--to=dan@mindstab.net \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=gorcunov@openvz.org \
--cc=kay.sievers@vrfy.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mvaliyav@redhat.com \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=peterz@infradead.org \
--cc=riel@redhat.com \
--cc=rob@landley.net \
--cc=tglx@linutronix.de \
--cc=xemul@parallels.com \
/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