From: Clark Williams <williams@redhat.com>
To: "Max Müller" <mxmr@gmx.net>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: Tweak Latency on Intel ATOM
Date: Mon, 15 Feb 2010 08:38:47 -0600 [thread overview]
Message-ID: <20100215083847.1a4a7ef0@torg> (raw)
In-Reply-To: <4B7914C6.8080005@gmx.net>
[-- Attachment #1: Type: text/plain, Size: 1049 bytes --]
On Mon, 15 Feb 2010 10:32:54 +0100
Max Müller <mxmr@gmx.net> wrote:
> >
> > I'd say you're doing pretty good keeping under 50us. You might want to
> > try it under a heavier load than the shell script you've been running.
> > If you don't want to fool with rteval, try kicking off a kernel compile
> > in another window like this:
> >
> > $ while true; do make -j4 clean bzImage modules; done
> >
> > and then run cyclictest. A kernel compile with parallel jobs (-j) is a
> > good overall load of computation and I/O.
> >
> >
>
> I tested now like you told me with irqbalance and cpuspeed services
> disabled. I hope i made the right for disabling irqbalance, i used the
> kernel parameter acpi_no_irqbalance. Is this correct? Unfortunately the
> results were nearly equal as before.
I don't think you're going to get much better results on the Atom. I
have an MSI Nettop box with the dual-core version and I saw about the
same results as you.
What sort of scheduling deadlines are you trying to meet?
Clark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2010-02-15 14:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-09 7:41 Tweak Latency on Intel ATOM Max Miller
2010-02-10 22:38 ` Clark Williams
2010-02-11 7:54 ` Max Müller
2010-02-11 15:34 ` Clark Williams
2010-02-15 9:32 ` Max Müller
2010-02-15 14:38 ` Clark Williams [this message]
2010-02-16 6:50 ` Max Müller
2010-02-16 12:18 ` Luis Claudio R. Goncalves
2010-02-17 6:26 ` Max Müller
2010-02-12 20:54 ` mapping of PCI memory to user space not working with uio.c ? Armin Steinhoff
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=20100215083847.1a4a7ef0@torg \
--to=williams@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=mxmr@gmx.net \
/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).