From: "J.R. Mauro" <jrm8005@gmail.com>
To: Chris Brannon <cmbrannon@cox.net>
Cc: john stultz <johnstul@us.ibm.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] /dev/time for Linux, inspired by Plan 9
Date: Thu, 12 Mar 2009 14:12:25 -0400 [thread overview]
Message-ID: <20090312181225.GC26099@tuxbookpro.rit.edu> (raw)
In-Reply-To: <20090307162327.PQGL18213.eastrmmtao106.cox.net@eastrmimpo02.cox.net>
On Sat, Mar 07, 2009 at 10:23:05AM -0600, Chris Brannon wrote:
> John Stultz wrote:
> > On Tue, Mar 3, 2009 at 7:06 PM, Christopher Brannon <cmbrannon@cox.net> wrote:
> > > I implemented such a facility for Linux. A read of /dev/time produces
> > > four decimal numbers: epoch seconds, nanoseconds since start of epoch,
> > > jiffies since boot, and jiffies per second.
> >
> > Ehh. Why would we want to export raw kernel internal values like
> > jiffies and HZ?
> >
> > I think the CLOCK_MONOTONIC clockid would probably be a better value to export.
>
> I'll look at CLOCK_MONOTONIC clockid. I'm more than glad to export something
> more appropriate, including nothing at all (dummy values, perhaps).
Chris, are the current values exactly what one would get if reading /dev/time on
Plan 9? If possible, it would be nice to aim for 100% compatibility as there are
folks trying to get complete Plan 9 binary compatibility working in Linux.
>
> -- Chris
> --
> 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/
--
J.R. Mauro
() ascii ribbon campaign - against html e-mail
/\ www.asciiribbon.org - against Microsoft attachments
next prev parent reply other threads:[~2009-03-12 18:12 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-04 3:06 Christopher Brannon
2009-03-06 17:57 ` Greg KH
2009-03-07 5:43 ` J.R. Mauro
2009-03-07 5:54 ` Greg KH
2009-03-07 16:08 ` Chris Brannon
2009-03-08 16:03 ` J.R. Mauro
2009-03-06 22:56 ` john stultz
2009-03-07 16:23 ` Chris Brannon
2009-03-12 18:12 ` J.R. Mauro [this message]
2009-03-14 23:27 ` Chris Brannon
2009-03-10 11:22 ` Pavel Machek
2009-03-11 7:28 ` Américo Wang
2009-03-11 15:10 Christopher Brannon
2009-03-11 21:49 ` Jochen Voß
2009-03-11 22:07 ` Bill Nottingham
2009-03-12 8:00 ` David Newall
2009-03-12 18:15 ` J.R. Mauro
2009-03-12 9:30 ` Giacomo A. Catenazzi
2009-03-14 16:13 ` Pavel Machek
2009-03-17 15:15 ` J.R. Mauro
2009-03-21 22:05 ` Pavel Machek
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=20090312181225.GC26099@tuxbookpro.rit.edu \
--to=jrm8005@gmail.com \
--cc=cmbrannon@cox.net \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.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®