public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frank Sorenson <frank@tuxrocks.com>
To: tglx@linutronix.de
Cc: LKML <linux-kernel@vger.kernel.org>,
	Steven Rostedt <rostedt@kihontech.com>,
	Con Kolivas <kernel@kolivas.org>,
	"high-res-timers-discourse@lists.sourceforge.net" 
	<high-res-timers-discourse@lists.sourceforge.net>,
	john cooper <john.cooper@timesys.com>,
	George Anzinger <george@mvista.com>,
	Doug Niehaus <niehaus@ittc.ku.edu>,
	john stultz <johnstul@us.ibm.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: [ANNOUNCE] ktimers high resolution patches - clockevent	abstraction layer
Date: Sat, 15 Oct 2005 01:17:30 -0600	[thread overview]
Message-ID: <4350AD0A.2010208@tuxrocks.com> (raw)
In-Reply-To: <1129328040.1728.829.camel@tglx.tec.linutronix.de>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thomas Gleixner wrote:
> i have released the 2.6.14-rc4-kthrt1 version of the high resolution
> timer enabled ktimers subsystem patch, which can be downloaded from

Great job.  I really like this rollup of ktimers + ktimersHRT + John's
TOD patches.

Initial results are showing excellent latency numbers.  I'll run some
tests overnight, and will report the results.

Frank
- --
Frank Sorenson - KD7TZK
Systems Manager, Computer Science Department
Brigham Young University
frank@tuxrocks.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFDUK0KaI0dwg4A47wRAg4JAKClGzgh0vGyt+yw0zoB5e3LoR82pwCfWgC7
L61GelaatdyczS8VbTKVWeQ=
=5Zb4
-----END PGP SIGNATURE-----

      reply	other threads:[~2005-10-15  7:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-14 22:14 [ANNOUNCE] ktimers high resolution patches - clockevent abstraction layer Thomas Gleixner
2005-10-15  7:17 ` Frank Sorenson [this message]

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=4350AD0A.2010208@tuxrocks.com \
    --to=frank@tuxrocks.com \
    --cc=george@mvista.com \
    --cc=high-res-timers-discourse@lists.sourceforge.net \
    --cc=john.cooper@timesys.com \
    --cc=johnstul@us.ibm.com \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=niehaus@ittc.ku.edu \
    --cc=rostedt@kihontech.com \
    --cc=tglx@linutronix.de \
    /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