All of lore.kernel.org
 help / color / mirror / Atom feed
From: Wolfgang Netbal <wolfgang.netbal@sigmatek.at>
To: xenomai@xenomai.org
Subject: Re: [Xenomai] Performance impact after switching from 2.6.2.1 to 2.6.4
Date: Tue, 28 Jun 2016 16:32:17 +0200	[thread overview]
Message-ID: <57728A71.6010205@sigmatek.at> (raw)
In-Reply-To: <20160628120119.GT18662@hermes.click-hack.org>



Am 2016-06-28 um 14:01 schrieb Gilles Chanteperdrix:
> On Tue, Jun 28, 2016 at 01:55:27PM +0200, Wolfgang Netbal wrote:
>>
>> Am 2016-06-28 um 12:39 schrieb Gilles Chanteperdrix:
>>> On Tue, Jun 28, 2016 at 12:31:42PM +0200, Wolfgang Netbal wrote:
>>>> Am 2016-06-28 um 12:19 schrieb Gilles Chanteperdrix:
>>>> min: 10, max: 677, avg: 10.5048 -> 0.0265273 us
>>>>
>>>> Here are the output for Kernel 3.0.43 and Xenomai 2.6.2.1
>>>>
>>>> #> ./tsc
>>>> min: 10, max: 667, avg: 11.5755 -> 0.029231 us
>>> Ok. So, first it confirms that the two configurations are running
>>> the processor at the same frequency. But we seem to see a pattern,
>>> the maxima in the case of the new kernel seems consistently higher.
>>> Which would suggest that there is some difference in the cache. What
>>> is the status of the two configurations with regard to the L2 cache
>>> write allocate policy?
>> Do you mean the configuration we checked in this request
>> https://xenomai.org/pipermail/xenomai/2016-June/036390.html
> This answer is based on a kernel message, which may happen before
> or after the I-pipe patch has changed the value passed to the
> register, so, essentially, it is useless. I would not call that
> checking the L2 cache configuration differences.
>
I readed the values from the auxiliary control register,
when the system is up and running.
I get the same values like I see in the Kernel log.

Kernel 3.10.53 [0xa02104]=0x32c50000
Kernel 3.0.43    [0xa02104]=0x2850000






  reply	other threads:[~2016-06-28 14:32 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-31 14:09 [Xenomai] Performance impact after switching from 2.6.2.1 to 2.6.4 Wolfgang Netbal
2016-05-31 14:16 ` Gilles Chanteperdrix
2016-06-01 13:52   ` Wolfgang Netbal
2016-06-01 14:12     ` Gilles Chanteperdrix
2016-06-02  8:15       ` Wolfgang Netbal
2016-06-02  8:23         ` Gilles Chanteperdrix
2016-06-06  7:03           ` Wolfgang Netbal
2016-06-06 15:35             ` Gilles Chanteperdrix
2016-06-07 14:13               ` Wolfgang Netbal
2016-06-07 17:00                 ` Gilles Chanteperdrix
2016-06-27 15:55                   ` Wolfgang Netbal
2016-06-27 16:00                     ` Gilles Chanteperdrix
2016-06-28  8:08                       ` Wolfgang Netbal
2016-06-27 16:46                     ` Gilles Chanteperdrix
2016-06-28  8:31                       ` Wolfgang Netbal
2016-06-28  8:34                         ` Gilles Chanteperdrix
2016-06-28  9:15                           ` Wolfgang Netbal
2016-06-28  9:17                             ` Gilles Chanteperdrix
2016-06-28  9:28                               ` Wolfgang Netbal
2016-06-28  9:29                                 ` Gilles Chanteperdrix
2016-06-28  9:51                                   ` Wolfgang Netbal
2016-06-28  9:55                                     ` Gilles Chanteperdrix
2016-06-28 10:10                                       ` Wolfgang Netbal
2016-06-28 10:19                                         ` Gilles Chanteperdrix
2016-06-28 10:31                                           ` Wolfgang Netbal
2016-06-28 10:39                                             ` Gilles Chanteperdrix
2016-06-28 11:45                                               ` Wolfgang Netbal
2016-06-28 11:57                                                 ` Gilles Chanteperdrix
2016-06-28 11:55                                               ` Wolfgang Netbal
2016-06-28 12:01                                                 ` Gilles Chanteperdrix
2016-06-28 14:32                                                   ` Wolfgang Netbal [this message]
2016-06-28 14:42                                                     ` Gilles Chanteperdrix
2016-06-30  9:17                                                       ` Wolfgang Netbal
2016-06-30  9:39                                                         ` Gilles Chanteperdrix
2016-06-07 17:22                 ` Philippe Gerum
2016-05-31 15:08 ` 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=57728A71.6010205@sigmatek.at \
    --to=wolfgang.netbal@sigmatek.at \
    --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.