From: Christoph Lameter <clameter@sgi.com>
To: Roland McGrath <roland@redhat.com>
Cc: Andrew Morton <akpm@osdl.org>, Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] back out CPU clock additions to posix-timers
Date: Sun, 19 Dec 2004 19:30:01 -0800 (PST) [thread overview]
Message-ID: <Pine.LNX.4.58.0412191923360.1580@schroedinger.engr.sgi.com> (raw)
In-Reply-To: <200412182202.iBIM2RaZ030987@magilla.sf.frob.com>
On Sat, 18 Dec 2004, Roland McGrath wrote:
> > Roland McGrath <roland@redhat.com> wrote:
> > >
> > > I really think we should not let the
> > > existing clockid_t encoding change get out in 2.6.10.
> >
> > So.. could you please send a patch which disables the userspace-visibility
> > of Christoph's changes?
I am not sure what the point of these is? The userspace visibility of the
regular posix clocks (positive clockid's) does not change. The way we
encode process cputime clocks as negative values changes but there is
nothing that supports my encoding yet (apart from my test code) since
the glibc patch was never accepted.
I would like to keep the support for all 4 standard posix clocks through
clockids 0-3 as listed in the kernel headers and simply have the cputime
clocks redirect to your code appropriately to get the current values for
each process. IMHO that makes the interface cleaner, is cleaner for glibc
since it allows simply to pass positive clockids through and also
maintains compatibility for positive clockids to the existing situation.
next prev parent reply other threads:[~2004-12-20 3:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20041216143312.6910521d.akpm@osdl.org>
2004-12-18 22:02 ` Roland McGrath
2004-12-20 3:30 ` Christoph Lameter [this message]
2004-12-20 3:45 ` Roland McGrath
2004-12-20 3:44 ` Christoph Lameter
2004-12-20 3:47 ` Roland McGrath
2004-12-20 17:00 ` Christoph Lameter
2004-12-20 19:37 ` Roland McGrath
2004-12-20 20:15 ` Christoph Lameter
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=Pine.LNX.4.58.0412191923360.1580@schroedinger.engr.sgi.com \
--to=clameter@sgi.com \
--cc=akpm@osdl.org \
--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
all inboxes | Powered by JetHome®