From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Michele Belotti <miki.belotti@gmail.com>
Cc: xenomai@xenomai.org
Subject: Re: [Xenomai] Fwd: Latency test fails. Problem during installation
Date: Mon, 7 Mar 2016 12:37:08 +0100 [thread overview]
Message-ID: <20160307113708.GA24055@hermes.click-hack.org> (raw)
In-Reply-To: <CANBp=-iWByct=fMOPB6u8PrS10h2M0w9MbaOGrJAvfGqsjCVCw@mail.gmail.com>
On Mon, Mar 07, 2016 at 11:33:31AM +0100, Michele Belotti wrote:
> Hello everybody,
> We recently migrated my project on a new and more powerful workstation but
> I can obtain the previous performance.
You mean you can NOT.
>
> We observed by running the standard Xenomai tools that there are very high
> latencies, hinting for an issue in the kernel configuration (or maybe
> unsupported HW features by Xenomai ?).
How high?
>
> We are trying to install Xenomai version 2.6.3 on a HP Z840 workstation Red
> Hat system 7.2.
> The Workstation has a double 12 cores CPU Intel Xeon E5-2690v3 on
> it.
Why installing Xenomai 2.6.3 ? It is not even the latest release in
the 2.6 branch.
>
> We follow the installation guide and the troubleshooting but the latency is
> still very high with some high jumps.
> We tried to deal with the different options described in the guide
>
> CONFIG_CPU_FREQ, CONFIG_CPU_IDLE, CONFIG_CONTEXT_TRACKING_FORCE
> XENO_OPT_STATS NO_HZ_FULL_ALL BSD_PROCESS_ACCT but none has impacted the
> system, only marginal improvements.
What about CONFIG_ACPI_CPUFREQ?
>
> We also tried to modify the SMI detection parameters adding the following
> string to kernel command line
> xeno_hal.smi = 1
> but without any effect.
I am not sure 2.6.3 already had the kernel parameters, you may have
to configure the kernel to enable the SMI workaround.
In any case, using the module parameter, if this works, should
trigger some messages in the boot logs, as explained in the
troubleshooting guide. If you do not see the messages, you are doing
it wrong.
Regards.
--
Gilles.
https://click-hack.org
next prev parent reply other threads:[~2016-03-07 11:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CANBp=-hcC5DHb=HpMzqbewQswwwh-dF-+i+DoOd6KRHoXbv2qw@mail.gmail.com>
2016-03-07 10:33 ` [Xenomai] Fwd: Latency test fails. Problem during installation Michele Belotti
2016-03-07 11:32 ` Henning Schild
2016-03-08 8:50 ` Michele Belotti
2016-03-09 15:12 ` Michele Belotti
2016-03-07 11:37 ` Gilles Chanteperdrix [this message]
2016-03-07 12:51 ` Gilles Chanteperdrix
2016-03-07 11:45 ` Philippe Gerum
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=20160307113708.GA24055@hermes.click-hack.org \
--to=gilles.chanteperdrix@xenomai.org \
--cc=miki.belotti@gmail.com \
--cc=xenomai@xenomai.org \
/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.