All of lore.kernel.org
 help / color / mirror / Atom feed
From: eric <ericvic@163.com>
To: Gilles Chanteperdrix <gilles.chanteperdrix@xenomai.org>
Cc: huang.c.h@lynuc.cn, liu.h.f@lynuc.cn,
	"xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: [Xenomai] imx6q xenomai ipipe-3.0-imx6q
Date: Sun, 20 Apr 2014 13:06:01 +0800 (CST)	[thread overview]
Message-ID: <59ece04.26b88.1457d86db18.Coremail.ericvic@163.com> (raw)
In-Reply-To: <535110C3.40500@xenomai.org>

So if my program use lots of memory operations  for a long time it maybe gives non real-time activities opportunity to thrash the cache?






--
发自我的网易邮箱平板适配版
<br/><br/><br/>


----- Original Message -----
From: "Gilles Chanteperdrix" <gilles.chanteperdrix@xenomai.org>
To: "嵌入式工程师" <ericvic@163.com>
Cc: "xenomai@xenomai.org" <xenomai@xenomai.org>, liu.h.f@lynuc.cn, huang.c.h@lynuc.cn
Sent: Fri, 18 Apr 2014 13:47:15 +0200
Subject: Re: imx6q xenomai ipipe-3.0-imx6q

On 04/18/2014 12:28 PM, 嵌入式工程师 wrote:
> 
> 
> I do the same on the imx53 with imx6 test, in the process of
> real-time task to run the same operation content, start the qt deform
> demo and copy large file  to memory, in 250 us the  latency on imx6
> board began to accumulate, lost real-time, but latency  on the imx53
> only value within 20 us. I do not run anyother rt task on my below
> test:

Looking at your code, it seems your problem (if I understand correctly),
is that a series of memcpy and memset takes a long time to execute when
non real-time activities are given an opportunity to thrash the cache.

Am I understanding correctly?

-- 
                                                                Gilles.

  reply	other threads:[~2014-04-20  5:06 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-18 10:28 [Xenomai] imx6q xenomai ipipe-3.0-imx6q 嵌入式工程师
2014-04-18 11:47 ` Gilles Chanteperdrix
2014-04-20  5:06   ` eric [this message]
2014-04-20  9:03     ` Gilles Chanteperdrix
2014-04-20  9:23       ` Gilles Chanteperdrix
2014-04-20 10:46         ` eric
2014-04-23  4:40           ` eric
2014-04-23 12:24             ` Gilles Chanteperdrix
  -- strict thread matches above, loose matches on Subject: below --
2014-04-17  8:13 嵌入式工程师
2014-04-17  7:58 嵌入式工程师
2014-04-17  7:43 嵌入式工程师
2014-04-17 11:42 ` Gilles Chanteperdrix
2014-04-01  2:35 嵌入式工程师
2014-04-01 10:49 ` Gilles Chanteperdrix
2014-04-02  0:53   ` 嵌入式工程师
2014-04-02  7:28     ` Gilles Chanteperdrix
2014-04-03 10:25       ` 嵌入式工程师
2014-03-26 11:36 嵌入式工程师
2014-03-26 11:50 ` Gilles Chanteperdrix
2014-03-26 13:31   ` 嵌入式工程师
2014-03-26 13:34     ` Gilles Chanteperdrix
2014-03-26 14:29       ` 嵌入式工程师
2014-03-26 23:09         ` Gilles Chanteperdrix
2014-03-27  1:41           ` 嵌入式工程师
2014-03-27  5:24           ` 嵌入式工程师
2014-03-27 12:27             ` Gilles Chanteperdrix
2014-03-28  5:02               ` 嵌入式工程师
2014-03-28 17:35                 ` Gilles Chanteperdrix
2014-03-29  5:54                   ` 嵌入式工程师
2014-03-28  8:19               ` 嵌入式工程师
2014-03-28 17:37                 ` Gilles Chanteperdrix
2014-03-28  9:08               ` 嵌入式工程师
2014-03-28 17:38                 ` Gilles Chanteperdrix
2014-03-29  6:21                   ` 嵌入式工程师
2014-03-29 13:51                     ` Gilles Chanteperdrix

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=59ece04.26b88.1457d86db18.Coremail.ericvic@163.com \
    --to=ericvic@163.com \
    --cc=gilles.chanteperdrix@xenomai.org \
    --cc=huang.c.h@lynuc.cn \
    --cc=liu.h.f@lynuc.cn \
    --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.