public inbox for ecos-cvs@sourceware.org
help / color / mirror / Atom feed
From: nickg@sourceware.org
To: ecos-cvs@ecos.sourceware.org
Subject: ecos/packages/kernel/current ChangeLog cdl/ker ...
Date: Mon, 08 Jan 2007 16:20:00 -0000 [thread overview]
Message-ID: <20070108162014.11876.qmail@sourceware.org> (raw)
CVSROOT: /cvs/ecos
Module name: ecos
Changes by: nickg@sourceware.org 2007-01-08 16:20:14
Modified files:
packages/kernel/current: ChangeLog
packages/kernel/current/cdl: kernel.cdl
packages/kernel/current/include: bitmap.hxx kapidata.h
mlqueue.hxx
packages/kernel/current/src/sched: mlqueue.cxx sched.cxx
packages/kernel/current/tests: timeslice.c tm_basic.cxx
Added files:
packages/kernel/current/tests: timeslice2.c
Log message:
* src/sched/mlqueue.cxx (add_thread, yield):
* src/sched/sched.cxx (unlock_inner, thread_entry):
* include/mlqueue.hxx (class Cyg_SchedThread_Implementation):
* include/kapidata.h (CYG_SCHEDTHREAD_TIMESLICE_MEMBER):
* include/bitmap.hxx (class Cyg_SchedThread_Implementation):
Reimplement timeslicing code. There is now a timeslice_count field
in each thread which is moved to and from the per-CPU counter
during thread dispatch. This approach has been taken to minimize
the changes needed to SMP code. Scheduler specific thread
functions handle counter save, restore and reset. These functions
are defined (as empty inlines) even when timeslicing is disabled,
or in non-timeslicing schedulers, to avoid adding ifdefs to the
code (this change actually removes some).
* tests/timeslice2.c:
* cdl/kernel.cdl: Added timeslice2 test to test behaviour of
timeslicing while being preempted.
next reply other threads:[~2007-01-08 16:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-08 16:20 nickg [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-03-09 18:06 vae
2003-07-01 17:34 nickg
2003-06-23 18:19 nickg
2003-01-31 11:44 nickg
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=20070108162014.11876.qmail@sourceware.org \
--to=nickg@sourceware.org \
--cc=ecos-cvs@ecos.sourceware.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 read-only IMAP folder(s) and NNTP newsgroup(s).