From: Carsten Emde <Carsten.Emde@osadl.org>
To: "Leyendecker, Robert" <Robert.Leyendecker@lsi.com>
Cc: Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>,
RT <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] [rt-tests] change to cyclictest behavior
Date: Thu, 07 Jan 2010 08:09:59 +0100 [thread overview]
Message-ID: <4B4588C7.2040706@osadl.org> (raw)
In-Reply-To: <8C8865ED624BB94F8FE50259E2B5C5B30459433B48@palmail03.lsi.com>
On 01/07/2010 01:30 AM, Leyendecker, Robert wrote:
>>> How about -m (mlockall) as well?
>> Hmm, I think that this one is less obvious. Apparently, there are
>> a bunch of different opinions on mlockall(). I once heard, for
>> example, the opinion that mlockall() may - under some conditions -
>> introduce a performance penalty, but I did not verify that. Many
>> real-time systems do not have a "swap" line in /etc/fstab;
>> mlockall() is not needed in such systems. In addition, most today's
>> systems have so much RAM that swapping became a rather rare event.
>> I hope some other RT-ers who are more knowledgeable about memory
>> management and swapping can comment on this.
> I have found mlockall() necessary. I alloc very large buffers for
> transmitting and capturing hundreds of voip streams. In my testing,
> if I don't mlockall() mostly following the advice on the rt-wiki
> (thanks for this life saver) network rt performance is unacceptable,
> jitter is 10X - 50X worse on my system. File system activity renders
> the system choppy and sluggish. All my memory is nailed up and
> preloaded where possible before I pull the trigger. I run on standard
> FC distro (with most services turned off). Getting good performance
> on a standard distro is amazing to me.
> Our test team has discovered that they get good network performance
> while simultaneously running wireshark and other apps like VNC. I
> think audio guys run huge x apps and full blown distros, while
> running 12+ channels of raw audio to disk. I can't see how they do it
> without mlock.
> [..]
Yes, of course. No one wants to drop the -m option. It was only the
question whether we include it into the new -S (equals -a -t -n -d plus
same priority on all) option which would make it impossible to run -S
without -m. In case it is decided not to include -m, you would need to
specify it separately, such as, for example
cyclictest -Sp99 -m
I would guess that this is acceptable, isn't it?
Carsten.
next prev parent reply other threads:[~2010-01-07 7:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-06 19:04 [RFC] [rt-tests] change to cyclictest behavior Clark Williams
2010-01-06 19:39 ` John Kacur
2010-01-06 21:39 ` Carsten Emde
2010-01-06 22:04 ` Clark Williams
2010-01-06 22:24 ` Carsten Emde
2010-01-06 22:27 ` Clark Williams
2010-01-06 22:50 ` Carsten Emde
2010-01-07 0:30 ` Leyendecker, Robert
2010-01-07 7:09 ` Carsten Emde [this message]
2010-01-07 7:23 ` Carsten Emde
2010-01-07 14:47 ` Clark Williams
2010-01-07 14:54 ` Carsten Emde
2010-01-12 16:59 ` Sven-Thorsten Dietrich
2010-01-12 17:04 ` Clark Williams
2010-01-12 17:13 ` Sven-Thorsten Dietrich
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=4B4588C7.2040706@osadl.org \
--to=carsten.emde@osadl.org \
--cc=Robert.Leyendecker@lsi.com \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=williams@redhat.com \
/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).