From: NavEcos <ecos@navosha.com>
To: Andrew Lunn <andrew.lunn@ascom.ch>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] simple eCos profiler
Date: Wed, 31 Jul 2002 01:38:00 -0000 [thread overview]
Message-ID: <02073101425401.16908@c1830598-a> (raw)
In-Reply-To: <20020731080529.GD3392@biferten.ma.tech.ascom.ch>
On Wednesday 31 July 2002 01:05, Andrew Lunn wrote:
> Hi Rich.
>
> This looks similar to the one i wrote a few years ago for eCos. Its
> sitting in the ecos-discuss archive somewhere. That was for the
> EBSA285, but could be easily ported to other targets. I find a
> profiler useful at times, so it would be good to get something
> incorporated.
I just want to get something basic, perhaps later on a more polished
tool can be made.
> > I would like to get at least hooks for this into the main tree. It
> > will not slow down eCos, it will be conditionally compilable. I
> > can do the CDL if requested. How do I get it into CVS?
>
> Post the patch to ecos-patches. We the community can then take a look
> at it and decide what needs doing to make it incorperatable, eg cdl,
> making it more generic etc.
There is a significant amount of code, most of it is not kernel code.
Is it OK if I post a link to a webpage? I just have to set one up :D
> > -Rich
> >
> > P.S. hal_ctrlc_check gets called a LOT and seems to get called
> > more, the more pings I send it. I haven't debugged this to find out
> > why, but it's perplexing. Anybody know what is going on with it?
>
> This function acts as the interface between the application network
> stack and redboot. Each packet received by the application is passed
> down to redboot to let it decide if the packet is actually for the
> redboot stack, not the application stack.
Oh. That name seem sort of obsfucated, but I get it.
I will have to look at this more. I have found that it can take up
significant time (like 33% of the active time) if I send enough
network traffic through it.
I have a question. When redboot "runs", can the application on
top of redboot interrupt it? I haven't investigated the relationship
between the two very much.
> Andrew
Thank you,
-Rich
--
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss
next prev parent reply other threads:[~2002-07-31 8:38 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-30 22:20 NavEcos
2002-07-31 1:05 ` Andrew Lunn
2002-07-31 1:38 ` NavEcos [this message]
2002-07-31 2:02 ` Andrew Lunn
2002-07-31 2:54 ` NavEcos
2002-07-31 3:13 ` Andrew Lunn
2002-07-31 4:55 ` Scott Dattalo
2002-07-31 5:19 ` Gary Thomas
2002-08-01 3:05 ` NavEcos
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=02073101425401.16908@c1830598-a \
--to=ecos@navosha.com \
--cc=andrew.lunn@ascom.ch \
--cc=ecos-discuss@sources.redhat.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).