All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
To: Jan Kiszka <jan.kiszka@domain.hid>,
	Juan Antonio Garcia Redondo <juan-antonio.garcia@domain.hid>,
	jagarcia@domain.hid, xenomai@xenomai.org
Subject: Re: [Xenomai-core] [Xenomai-help] AT91SAM9260 latency
Date: Tue, 12 Feb 2008 08:53:08 +0100	[thread overview]
Message-ID: <18353.20580.55980.279684@domain.hid> (raw)
In-Reply-To: <18353.17667.156910.185055@domain.hid>

Gilles Chanteperdrix wrote:
 > 
 > And another here, whereas if I understand correctly, the mm did not
 > change. So, this is probably an unwanted effect of the cache flush
 > "optimization" in the arm patch.
 > 
 > I will now try to understand if this second cache flush is really normal.

Yes, it is normal: the first context switch, which xnshadow_relax does,
is a switch to whatever task Linux was running when preempted, not
necessarily latency (and it turns out to never be latency when we
capture the worst case) hence the first cache flush. We then re-interrupt
Linux after this context switch, and switch again to latency, and we get
a second cache flush.

So, the conclusion is: everything is normal. What we obtain when
pressing the enter key while latency is running in the background is a
wakeup of the shell process and this process uses cache, so that the
next latency context switches need to flush cache.

In other words: pressing the enter key yields the same latency as
running the cache calibrator because it has the same effect, it fills
the cache.

-- 


					    Gilles Chanteperdrix.


      reply	other threads:[~2008-02-12  7:53 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-23  6:52 [Xenomai-help] AT91SAM9260 latency Juan Antonio Garcia Redondo
2008-01-23 10:04 ` Gilles Chanteperdrix
2008-01-23 13:15   ` Gilles Chanteperdrix
2008-01-24  9:41     ` Juan Antonio Garcia Redondo
2008-01-24 10:02       ` Gilles Chanteperdrix
2008-01-25 10:04         ` Juan Antonio Garcia Redondo
2008-01-25 17:00           ` Gilles Chanteperdrix
2008-01-28  8:51             ` Juan Antonio Garcia Redondo
2008-01-28  9:21               ` Juan Antonio Garcia Redondo
2008-01-28 13:19               ` Gilles Chanteperdrix
2008-01-28 13:34                 ` Jan Kiszka
2008-01-28 13:35                   ` Gilles Chanteperdrix
2008-01-28 13:46                     ` Jan Kiszka
2008-01-28 13:51                       ` Gilles Chanteperdrix
2008-01-28 14:10                         ` Jan Kiszka
2008-01-29  8:09                 ` Juan Antonio Garcia Redondo
2008-01-29  8:35                   ` Gilles Chanteperdrix
2008-01-29 17:19                   ` Gilles Chanteperdrix
2008-01-30  9:03                     ` Juan Antonio Garcia Redondo
2008-02-10 20:31       ` [Xenomai-core] " Gilles Chanteperdrix
2008-02-11 13:41         ` Jan Kiszka
2008-02-11 14:05           ` Gilles Chanteperdrix
2008-02-11 17:11             ` Jan Kiszka
2008-02-11 21:30               ` Gilles Chanteperdrix
2008-02-11 22:36               ` Gilles Chanteperdrix
2008-02-12  7:04           ` Gilles Chanteperdrix
2008-02-12  7:53             ` Gilles Chanteperdrix [this message]

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=18353.20580.55980.279684@domain.hid \
    --to=gilles.chanteperdrix@xenomai.org \
    --cc=jagarcia@domain.hid \
    --cc=jan.kiszka@domain.hid \
    --cc=juan-antonio.garcia@domain.hid \
    --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.