From: George Anzinger <george@mvista.com>
To: Roland McGrath <roland@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org,
Christoph Lameter <clameter@sgi.com>,
Ulrich Drepper <drepper@redhat.com>
Subject: Re: [PATCH 4/7] posix-timers: CPU clock support for POSIX timers
Date: Mon, 24 Jan 2005 18:31:14 -0800 [thread overview]
Message-ID: <41F5AF72.8000502@mvista.com> (raw)
In-Reply-To: <200501232325.j0NNPUg7006501@magilla.sf.frob.com>
Roland McGrath wrote:
> POSIX requires that when you claim _POSIX_CPUTIME and _POSIX_THREAD_CPUTIME,
> not only the clock_* calls but also timer_* calls must support the thread
> and process CPU time clocks. This patch provides that support, building on
> my recent additions to support these clocks in the POSIX clock_* interfaces.
> This patch will not work without those changes, as well as the patch fixing
> the timer lock-siglock deadlock problem.
>
> The apparent pervasive changes to posix-timers.c are simply that some
> fields of struct k_itimer have changed name and moved into a union.
> This was appropriate since the data structures required for the existing
> real-time timer support and for the new thread/process CPU-time timers are
> quite different.
Possibly you could bury these name changes in defines. I suspect the code would
be easier to read and that we really don't need to be reminded that it is a
union on each reference.
--
George Anzinger george@mvista.com
High-res-timers: http://sourceforge.net/projects/high-res-timers/
next prev parent reply other threads:[~2005-01-25 2:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-23 23:25 [PATCH 4/7] posix-timers: CPU clock support for POSIX timers Roland McGrath
2005-01-25 2:31 ` George Anzinger [this message]
2005-01-25 2:35 ` Christoph Lameter
2005-01-25 22:52 ` Christoph Lameter
2005-01-25 23:17 ` Roland McGrath
2005-01-25 23:39 ` George Anzinger
2005-01-25 23:48 ` Christoph Lameter
2005-01-26 1:04 ` Chris Wedgwood
2005-01-25 23:15 ` Roland McGrath
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=41F5AF72.8000502@mvista.com \
--to=george@mvista.com \
--cc=akpm@osdl.org \
--cc=clameter@sgi.com \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=torvalds@osdl.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;
as well as URLs for NNTP newsgroup(s).