From: Andrea Acquaviva <aacquaviva@deis.unibo.it>
To: "ecos-discuss@sources.redhat.com" <ecos-discuss@sources.redhat.com>
Subject: [ECOS]thread switch frequency
Date: Fri, 20 Apr 2001 01:59:00 -0000 [thread overview]
Message-ID: <3ADFFA65.CC964CFF@deis.unibo.it> (raw)
Hi,
I have a question about eCos mlqueue scheduler.
If there are two threads (making a matrix multiplication), running with
the same priority, they switch with a frequency given by:
f_clock/CYGNUM_KERNEL_SCHED_TIMESLICE_TICKS,
where f_clock in the case of strongarm1110 (assabet) is 3.6864MHz.
Is this correct or is there something else that affects the switching
frequency?
My question arises because I observed a mismatch between the switch time
overhead calculated by tm_basic test and the one that I measured by
evaluating the execution time of the two thread mentioned above (that
is, is much less than expected).
Thanks!
Andrea.
--
Ing. Andrea Acquaviva
D.E.I.S. - Universita' di Bologna
V.le Risorgimento, 2 40136 BOLOGNA (ITALY)
Tel: (+39) 051 20 93787 Fax: (+39) 051 2093786
next reply other threads:[~2001-04-20 1:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-20 1:59 Andrea Acquaviva [this message]
2001-04-20 2:23 ` Jonathan Larmour
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=3ADFFA65.CC964CFF@deis.unibo.it \
--to=aacquaviva@deis.unibo.it \
--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).