From: Clark Williams <clark.williams@gmail.com>
To: Robert de Vries <robert.h.de.vries@gmail.com>
Cc: Thomas Gleixner <tglx@linutronix.de>,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Luis Claudio Goncalves <lclaudio@uudg.org>,
RT <linux-rt-users@vger.kernel.org>
Subject: Re: add mlockall option to cyclictest, et al
Date: Sat, 10 May 2008 14:30:35 -0500 [thread overview]
Message-ID: <4825F7DB.6000808@gmail.com> (raw)
In-Reply-To: <4825F5AF.7010700@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robert de Vries wrote:
> Clark Williams wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Thomas,
>>
>> Got a couple of requests for mlockall() in cyclictest, so I added an
>> --mlockall
>> option to cyclictest, signaltest and pi_stress.
>>
> One small remark: it would be better to do the mlockall() by default. As
> far as I know this should be done always for real-time applications.
> I am actually surprised that it is not done already. It is also
> mentioned in the Howto build an RT-application on the RT linux wiki.
>
> Robert
>
>
I thought about that, but figured it would be better just to have the option rather
than change long-standing behavior.
It's Thomas's call though :)
Clark
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iEYEARECAAYFAkgl99sACgkQqA4JVb61b9eV4gCgiIs5QHocKBRHyOsGlMw+F5BA
PuUAnRo5+9oeO5oMFjq55JUxaR7dBI2b
=pefi
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2008-05-10 19:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-09 18:55 add mlockall option to cyclictest, et al Clark Williams
2008-05-09 21:04 ` Sven-Thorsten Dietrich
2008-05-10 19:21 ` Robert de Vries
2008-05-10 19:30 ` Clark Williams [this message]
2008-05-25 21:22 ` Thomas Gleixner
2008-07-08 8:49 ` Daniel Gollub
2008-07-09 13:10 ` Thomas Gleixner
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=4825F7DB.6000808@gmail.com \
--to=clark.williams@gmail.com \
--cc=acme@ghostprotocols.net \
--cc=lclaudio@uudg.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=robert.h.de.vries@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.