From: Clark Williams <williams@redhat.com>
To: RT <linux-rt-users@vger.kernel.org>
Cc: LKML <linux-kernel@vger.kernel.org>, "Carsten Emde" <ce@ceag.ch>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"John Kacur" <jkacur@redhat.com>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: [rt-tests] version 0.63 available
Date: Wed, 27 Jan 2010 10:23:54 -0600 [thread overview]
Message-ID: <20100127102354.0b5c0f9d@torg> (raw)
[-- Attachment #1: Type: text/plain, Size: 1385 bytes --]
The latest version of rt-tests is now available as a tarball from:
http://www.kernel.org/pub/linux//kernel/people/clrkwllms/rt-tests/rt-tests-0.63.tar.bz2
Also available in my git repo:
git://git.kernel.org/pub/scm/linux/kernel/git/clrkwllms/rt-tests.git
under tag v0.63
This version includes a new option: --numa, which is a counterpart to
the recently introduced --smp option.
The --smp option is a shorthand for: -t -a -n, meaning that one
measurement thread is created per active CPU and is affined to that cpu
and that clock_nanosleep is used for measurements.
The --numa option does the same options as --smp, but also makes calls
into libnuma to ensure that measurement threads are always bound to the
memory node that is local to it's cpu (avoiding cross-node memory
references). Each measurement thread's stack and major data structures
are allocated from the local memory node.
Note that to actually use --numa mode, you must pass NUMA=1 to the make
build command:
$ make NUMA=1
This is for all you embedded guys that could care less about NUMA :)
Other changes from previous releases are that the hwlatdetect test has
been moved to the python site-library (so that other tests can import
it) and then symlinked to /usr/bin/hwlatdetect. Also, copyright
messages have been updated in the source files (thanks Uwe).
Clark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
reply other threads:[~2010-01-27 16:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100127102354.0b5c0f9d@torg \
--to=williams@redhat.com \
--cc=ce@ceag.ch \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=u.kleine-koenig@pengutronix.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;
as well as URLs for NNTP newsgroup(s).