From: Matt Helsley <matthltc@us.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Andrew Morton <akpm@osdl.org>,
Jean-Pierre Dion <jean-pierre.dion@bull.net>,
Guillaume Thouvenin <guillaume.thouvenin@bull.net>,
Badari Pulavarty <pbadari@us.ibm.com>,
Ram Pai <linuxram@us.ibm.com>,
CKRM-Tech <ckrm-tech@lists.sourceforge.net>,
Erich Focht <efocht@hpce.nec.com>,
elsa-devel <elsa-devel@lists.sourceforge.net>,
Jay Lan <jlan@engr.sgi.com>, Erik Jacobson <erikj@sgi.com>,
Jack Steiner <steiner@sgi.com>
Subject: [RFC][PATCH 000/002] Add timestamp to process event connector message
Date: Mon, 05 Dec 2005 21:00:25 -0800 [thread overview]
Message-ID: <1133845225.25202.1373.camel@stark> (raw)
This series of patches adds a timestamp field to the events sent
via the process event connector. The timestamp allows listeners to
accurately account the duration(s) between a process' events and offers
strong means with which to determine the order of events while also
avoiding the addition of per-task data.
Series:
getnstimestamp.patch
proc-events-timestamp.patch
The first patch adds a new generic function, getnstimestamp(),
which gets an SMP-safe high-resolution monotonic timestamp.
The second patch adds a timestamp field to the events sent via
the process event connector and fills the field using the new timestamp
function. It alters the size and layout of the event structure and hence
would break compatibility if not incorporated with the first release of
process events connector in a mainline kernel.
Cheers,
-Matt Helsley
next reply other threads:[~2005-12-06 5:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-06 5:00 Matt Helsley [this message]
2005-12-06 5:05 ` [RFC][PATCH 001/002] Add getnstimestamp function Matt Helsley
2005-12-06 5:06 ` [RFC][PATCH 002/002] Add timestamp field to process events Matt Helsley
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=1133845225.25202.1373.camel@stark \
--to=matthltc@us.ibm.com \
--cc=akpm@osdl.org \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=efocht@hpce.nec.com \
--cc=elsa-devel@lists.sourceforge.net \
--cc=erikj@sgi.com \
--cc=guillaume.thouvenin@bull.net \
--cc=jean-pierre.dion@bull.net \
--cc=jlan@engr.sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxram@us.ibm.com \
--cc=pbadari@us.ibm.com \
--cc=steiner@sgi.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