public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
From: Jonathan Larmour <jlarmour@redhat.com>
To: "Pamulapati, Indrasena (CTS)" <pindrase@chn.cognizant.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS]  Performance comparision
Date: Tue, 06 Feb 2001 06:55:00 -0000	[thread overview]
Message-ID: <3A801046.69FBFD1E@redhat.com> (raw)
In-Reply-To: <8F1D166D08ACD41196EE00B0D020944BABA7C6@CTSINENTSXUB>

"Pamulapati, Indrasena (CTS)" wrote:
> 
> > Hi,
> >
> > I am the same guy who asked about the problem of having a very high tick
> > rate for addressing very small time units.
> > I now perfectly understand the futility of increasing the tick rate to
> > very high value and have decided to use external timers to address small
> > time frames.
> >
> > But just for comparision, I ported my application to VRTXsa a different
> > RTOS. And I used the same high tick rate ( about 10000 ticks per second)
> > and the application was running fine. I was able to acheive the bit rate
> > of about 20Mbps that I was suppose to acheive. But in eCos with such high
> > tick value I was able to acheive only 4Mbps.
> >
> > In reply to my previous mail I understood that if we use a very high tick
> > value a lot of processor resources will be spent on processing the tick
> > only and my application will suffer. But why am i not facing the same
> > problem in VRTXsa?
> >
> > Is it a limitation of eCos?

It's impossible to tell because it depends on how the driver and handler
was coded. Since at worst eCos allows you to write a VSR in assembly to
handle the interrupt, I would be surprised if performance could be bettered
in that situation.

Jifl
-- 
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine

  reply	other threads:[~2001-02-06  6:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-06  5:50 Pamulapati, Indrasena (CTS)
2001-02-06  6:55 ` Jonathan Larmour [this message]
2001-02-06  8:22 Pamulapati, Indrasena (CTS)

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=3A801046.69FBFD1E@redhat.com \
    --to=jlarmour@redhat.com \
    --cc=ecos-discuss@sources.redhat.com \
    --cc=pindrase@chn.cognizant.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).