public inbox for pthreads-win32@sourceware.org
 help / color / mirror / Atom feed
From: Ross Johnson <Ross.Johnson@homemail.com.au>
To: Stefan.Pusl@comneon.com
Cc: pthreads-win32@sourceware.org
Subject: Re: Supported scheduling policies?
Date: Fri, 05 Jan 2007 01:16:00 -0000	[thread overview]
Message-ID: <459DA6D9.7070600@homemail.com.au> (raw)
In-Reply-To: <795528E59064E1439DF52D15EE769D5602E24B8A@mucse306.eu.infineon.com>

Stefan.Pusl@comneon.com wrote:
> Hello,
>
> I have noticed from the comformance list, that the only supported
> scheduling policy is SCHED_OTHER. Is there any action ongoing to support
> the scheduling policy SCHED_FIFO?
>   
Pthreads-win32 threads are just Windows threads and Win32 only has one 
scheduling policy that most appropriately corresponds to SCHED_OTHER. 
This assumes that Win32 can't somehow be made to emulate the POSIX 
required details of SCHED_FIFO, and that we can't just pretend to accept 
it for source code compatibility.

Ross

      reply	other threads:[~2007-01-05  1:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-04 14:32 Stefan.Pusl
2007-01-05  1:16 ` Ross Johnson [this message]

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=459DA6D9.7070600@homemail.com.au \
    --to=ross.johnson@homemail.com.au \
    --cc=Stefan.Pusl@comneon.com \
    --cc=pthreads-win32@sourceware.org \
    /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).