This is the mail archive of the ecos-discuss@sources.redhat.com mailing list for the eCos project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Replace eCos idle thread

From: Andrew Lunn <andrew at lunn dot ch>
To: Chris Garry <cgarry at sweeneydesign dot co dot uk>
Cc: Daniel Lidsten <Daniel dot Lidsten at combitechsystems dot com>,ecos-discuss at sources dot redhat dot com
Date: Fri, 12 Sep 2003 12:55:42 +0200
Subject: Re: [ECOS] Replace eCos idle thread
References: <004B1D7A5257174C9044A1B7BD0E60EDDAE725@ratatosk.combitechsystems.com> <007801c3791b$1ba8efc0$500ba8c0@jasper> <008401c3791b$880a4c40$500ba8c0@jasper>

> > You could just increase the number of priority levels.
> >  CYGNUM_KERNEL_SCHED_PRIORITIES
> > 
> 
> Okay - just spotted 32 is the max allowed.

Yep, it uses a bitmap in a uint32.

It would take some effort, but you could change this to uint64 so
doubling the number of levels.

If you only ever have one thread per level, you could use the bitmap
scheduler. That is simpler and will take less work to use a uint64.

      Andrew

-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss

References:
- RE: Replace eCos idle thread
  - From: Daniel Lidsten
- Re: Replace eCos idle thread
  - From: Chris Garry
- Re: Replace eCos idle thread
  - From: Chris Garry

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]