From: Wolfgang Denk <wd@denx.de>
To: Zajac Adam-AAZ004 <Adam.Zajac@motorola.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Help on tuning the Linux kernel for soft real-time requiremen ts
Date: Fri, 22 Oct 2004 00:34:04 +0200 [thread overview]
Message-ID: <20041021223409.7BD1EC146A@atlas.denx.de> (raw)
In-Reply-To: Your message of "Thu, 21 Oct 2004 16:55:13 CDT." <EFB813091B18D511BD3600508B644F820A618202@tx14exm06.ftw.mot.com>
In message <EFB813091B18D511BD3600508B644F820A618202@tx14exm06.ftw.mot.com> you wrote:
>
> Gerald, you may be right about this. Although I still don't know which of
> the threads in our system cause the serial resource contention, I
Check the console driver first.
> BTW, are you guys aware of any tool that could help me debug the threads
> that would concurrently try to access shared resources?
> Do you think LTT would be helpful for this particular problem (serial driver
LTT is certaily useful; but be aware that it may generate a of data
in short time, which then needs a lot of work to really understand
what's going on ;-)
> contention that leads to missing soft real-time deadlines)?
I'm not exaclty sure I really understand what you are asking for.
Isn't sometimes missing the deadlines what the "soft" is standing
for? ;-)
Best regards,
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de
There's another way to survive. Mutual trust -- and help.
-- Kirk, "Day of the Dove", stardate unknown
next prev parent reply other threads:[~2004-10-21 22:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 21:55 Help on tuning the Linux kernel for soft real-time requiremen ts Zajac Adam-AAZ004
2004-10-21 22:34 ` Wolfgang Denk [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-22 18:59 Zajac Adam-AAZ004
2004-10-22 19:10 ` Wolfgang Denk
2004-10-18 22:44 Zajac Adam-AAZ004
2004-10-19 1:51 ` Eugene Surovegin
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=20041021223409.7BD1EC146A@atlas.denx.de \
--to=wd@denx.de \
--cc=Adam.Zajac@motorola.com \
--cc=linuxppc-embedded@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).