From: Jesper Skov <jskov@redhat.com>
To: Paleologos Spanos <paleolog@ee.ucla.edu>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Unique priorities
Date: Wed, 10 Jan 2001 23:53:00 -0000 [thread overview]
Message-ID: <ot8zoi8r0a.fsf@thinktwice.zoftcorp.dk> (raw)
In-Reply-To: <Pine.GSO.4.10.10101101612370.20633-100000@sierra.ee.ucla.edu>
>>>>> "Paleologos" == Paleologos Spanos <paleolog@ee.ucla.edu> writes:
Paleologos> mlqueues default scheduler). I would expect that I would
Paleologos> have an error or something like that because of the fact
Paleologos> that the 2 threads are having the same priority (4).Is it
Paleologos> correct or I have misunderstood something?
The bitmap scheduler will assign a thread the closest possible
priority to that requested. It does not fail if the requested priority
is already used, it just returns another. So your threads would
probably have priorities 4 and 5.
Jesper
next prev parent reply other threads:[~2001-01-10 23:53 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 16:25 Paleologos Spanos
2001-01-10 23:53 ` Jesper Skov [this message]
2001-01-11 8:56 ` Jonathan Larmour
2001-01-11 9:15 ` Nick Garnett
2001-01-11 9:31 ` Dan Conti
2001-01-11 9:31 ` Jesper Skov
2001-01-11 9:35 ` Jonathan Larmour
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=ot8zoi8r0a.fsf@thinktwice.zoftcorp.dk \
--to=jskov@redhat.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=paleolog@ee.ucla.edu \
/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).