All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Gallagher <greg@embeddedgreg.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: "Xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: arm/arm64 ipipe performance
Date: Tue, 18 May 2021 15:06:52 -0400	[thread overview]
Message-ID: <CALLqZ8R=tb5h7rkqnV9WYJZWSY2xMNRtdWZhzR1oCmkjJs0YQA@mail.gmail.com> (raw)
In-Reply-To: <82f01d0d-360b-0016-9aec-24ef5b1a8d6b@siemens.com>

On Tue, May 18, 2021 at 2:49 PM Jan Kiszka <jan.kiszka@siemens.com> wrote:

> On 18.05.21 20:28, Greg Gallagher via Xenomai wrote:
> > Hi Everyone,
> >    There's been a noticeable slow down in the arm and arm64 latency of
> > late.  I tracked the issue
> >  down to the tracing infrastructure.  For now if you hit this issue,
> > disable ftrace.  Once this is done the latency numbers look much better.
> > I'm currently working on resolving the issue.
>
> Do you mean disabling during build? Or is the issue only present when
> tracing is actively used during runtime?




>
> >
> >   New patches will be released this week for both arm and arm64 now that
> > the issue is understood and a work around exists.
> >
>
> That's great!
>
> Jan
>
> --
> Siemens AG, T RDA IOT
> Corporate Competence Center Embedded Linux


Hi,
   I mean disabled during build time. That’s at least how I tested to see
that the issue went away. Hopefully I’ll have a solution soon.

Thanks

Greg

  reply	other threads:[~2021-05-18 19:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-18 18:28 arm/arm64 ipipe performance Greg Gallagher
2021-05-18 18:49 ` Jan Kiszka
2021-05-18 19:06   ` Greg Gallagher [this message]
2021-05-20 19:14     ` Robert Berger
2021-05-25 10:43 ` liandao
2021-05-25 13:21   ` Greg Gallagher

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='CALLqZ8R=tb5h7rkqnV9WYJZWSY2xMNRtdWZhzR1oCmkjJs0YQA@mail.gmail.com' \
    --to=greg@embeddedgreg.com \
    --cc=jan.kiszka@siemens.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.