* [ECOS] scheduler locking in Cyg_WallClock class
@ 2005-09-17 8:35 Daniel Helgason
0 siblings, 0 replies; only message in thread
From: Daniel Helgason @ 2005-09-17 8:35 UTC (permalink / raw)
To: ecos-discuss
I have a question about cyg_drv_dsr_lock() in
Cyg_WallClock::get_current_time in wallclock.cxx.
The comments in wallclock.cxx say the calls to the hardware drivers can take
a lot of time. And mine do - my RTC is an i2c device (relatively slow). The
whole scheduler is locked for the entire time it takes to read/write from
it.
Shouldn't the decision to take this drastic of a lock be in the lower-layer
driver?
I'm guessing the scheduler lock is to protect against possible interaction
between Cyg_WallClock::get_current_time and Cyg_WallClock::set_current_time
without having to use a mutex.
+---------------------------------------
| Daniel Helgason <danielh_AT_telus.net>
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2005-09-16 19:32 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-09-17 8:35 [ECOS] scheduler locking in Cyg_WallClock class Daniel Helgason
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).