This is the mail archive of the
ecos-discuss@sourceware.org
mailing list for the eCos project.
Re: Add new class to the scheduler file
- From: Nodir Kodirov <nodir dot qodirov at gmail dot com>
- To: John Dallaway <john at dallaway dot org dot uk>
- Cc: eCos Discussion <ecos-discuss at ecos dot sourceware dot org>
- Date: Wed, 12 May 2010 18:26:34 +0900
- Subject: [ECOS] Re: Add new class to the scheduler file
- References: <t2x186ad4051004200230r1adb154fo9815a8c6909ef633@mail.gmail.com> <4BEA6E3E.1090509@dallaway.org.uk>
Hello Mr. John!
> ...Any time-related scheduling constraints should be expressed in ticks...
This is what I did as a solution. I changed my approach to get job
done and now it is alright! As you told, I used only system clock
ticks, thus didn't need in Milli seconds.
I appreciate you response, thank you very much!
Regards,
Nodir.
On 12 May 2010 18:00, John Dallaway wrote:
Hi Nodir
Nodir Kodirov wrote:
> My aim is to store "millisecond per system tick" as a static member of
> some "general info class".
You really should not be concerned with time except at the level of the
system tick within the kernel. Any time-related scheduling constraints
should be expressed in ticks. Why do you need to know time in milliseconds?
John Dallaway
eCos maintainer
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss