Message-ID: <20051115102425.0iln2874xjoc4g84@coolrunningconcepts.com>
Date: Tue, 15 Nov 2005 10:24:25 -0700
From: evan@coolrunningconcepts.com
To: linux-kernel@vger.kernel.org
Subject: Timer idea
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.3)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 938
Lines: 18

I was thinking about benchmarking, profiling, and various other applications
that might need frequent access to the current time.  Polling timers or
frequent timer signal delivery both seem like there would be a lot of overhead.
 I was thinking it would be nice if you could just read the time information
without making an OS call.

I figure the kernel keeps accurate records of current time information and the
values of various timers.  I then had the idea that one could have a /dev or
maybe a /proc entry that would allow you to mmap() the kernel records (read
only) and then you could read this information right from the kernel without
any overhead.

Comments?  Please CC me on replies.
-
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/