This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: eCos scheduler
- From: Andrew Lunn <andrew at lunn dot ch>
- To: "Meulendijks, J." <Meulendijks at WT dot TNO dot NL>
- Cc: "'ecos-discuss at sources dot redhat dot com'" <ecos-discuss at sources dot redhat dot com>
- Date: Thu, 11 Nov 2004 16:43:09 +0100
- Subject: Re: [ECOS] eCos scheduler
- References: <6B80E71673E6D611AC1D0008C7F37BC203F8E603@wt15.wt.tno.nl>
On Thu, Nov 11, 2004 at 04:05:16PM +0100, Meulendijks, J. wrote:
> I checked in the ecos configuration and if I'm right then the clock should be
> running. Is there an other way to figure out if the clock really is running??
Run the tests i suggested. clocktruth and the other clock tests will
soon tell you if the clock is not working.
Andrew
>
> -----Original Message-----
> From: Andrew Lunn [mailto:andrew@lunn.ch]
> Sent: donderdag 11 november 2004 14:06
> To: Meulendijks, J.
> Cc: 'ecos-discuss@sources.redhat.com'
> Subject: Re: [ECOS] eCos scheduler
>
>
> On Thu, Nov 11, 2004 at 01:13:14PM +0100, Meulendijks, J. wrote:
> > Hi all,
> >
>
> > I have a question about time slicing. When I create two threads (A
> > and B) the scheduler will first run thread A (for example) and if
> > thread A has nothing to do any more thread B is executed. But when
> > thread A always has something to do thread B will never be executed!
> > Why?
> > I have enabled the mlqueue scheduler, both A and B have priority 4 and time
> > slicing is enabled.
>
> With this setup both should get to run, with a time slice of 50ms by
> default. If timeslicing is not happening it could be your clock is not
> working. Try running the kernel test program thread2 and clocktruth.
>
> Andrew
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss