From: Oleg Verych <olecom@flower.upol.cz>
To: linux-kernel@vger.kernel.org
Subject: Re: Linux time code
Date: Wed, 16 Aug 2006 14:36:28 +0200 [thread overview]
Message-ID: <44E3114C.1010808@flower.upol.cz> (raw)
In-Reply-To: <44E32B23.16949.BBB1EC4@Ulrich.Windl.rkdvmks1.ngate.uni-regensburg.de>
Ulrich Windl wrote:
> Hi everybody!
>
> I've been viewing recent changes to the Linux kernel (specifically 2.6.15.1 to
> 2.6.17.8), and I felt I'll have to say something:
>
> First there's a new routine in kernel/time.c named "set_normalized_timespec()".
[..something....]
> Sorry if you don't like that kind of message, but I just had to say that. It seems
> the time subsystem is already so complex that people are just adding new code
> instead of considering redesign or reuse of the existing code.
>
As far as i can see here's "return -ENOPATCH;" kind of mail list.
Did you read and consider cooperation with authors of:
"We Are Not Getting Any Younger: A New Approach to Time and Timers"
<http://www.linuxsymposium.org/2005/linuxsymposium_procv1.pdf>
"Hrtimers and Beyond: Transforming the Linux Time"
Subsystems <https://ols2006.108.redhat.com/reprints/gleixner-reprint.pdf> ?
> Regards,
> Ulrich
>
--
-o--=O`C
#oo'L O
<___=E M
next prev parent reply other threads:[~2006-08-16 14:36 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-16 12:26 Ulrich Windl
2006-08-16 12:36 ` Oleg Verych [this message]
2006-08-16 15:35 ` H. Peter Anvin
2006-08-16 15:12 ` Oleg Verych
2006-08-16 19:53 ` john stultz
2006-08-17 7:20 ` Ulrich Windl
2006-08-17 19:15 ` john stultz
2006-08-17 11:43 ` Roman Zippel
2006-08-17 21:58 ` john stultz
2006-08-17 22:11 ` Jesse Barnes
2006-08-17 22:32 ` john stultz
2006-08-17 22:50 ` Jesse Barnes
2006-08-17 23:02 ` john stultz
2006-08-20 17:14 ` Roman Zippel
2006-08-20 17:10 ` Roman Zippel
2006-08-23 6:25 linux
2006-08-23 18:29 ` john stultz
2006-08-24 2:35 ` linux
2006-08-28 11:39 ` Roman Zippel
2006-08-28 22:36 ` john stultz
2006-08-29 3:28 ` linux
2006-08-29 13:15 ` Theodore Tso
2006-08-29 15:18 ` linux
2006-08-29 19:23 ` john stultz
2006-08-29 14:43 ` Roman Zippel
2006-08-26 0:17 ` linux
2006-08-28 22:41 ` john stultz
2006-08-26 3:46 ` linux
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=44E3114C.1010808@flower.upol.cz \
--to=olecom@flower.upol.cz \
--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®