From: "Lee Revell" <rlrevell@joe-job.com>
To: "Evgeniy Polyakov" <johnpol@2ka.mipt.ru>
Cc: linux-kernel@vger.kernel.org, libc-hacker@sources.redhat.com,
libc-alpha@sources.redhat.com
Subject: Re: [ANN] Userspace M-on-N threading model implementation. Alpha release.
Date: Wed, 31 Jan 2007 23:28:07 -0500 [thread overview]
Message-ID: <75b66ecd0701312028w7866c608hbf70593055c92b19@mail.gmail.com> (raw)
In-Reply-To: <20070129145227.GA10524@2ka.mipt.ru>
On 1/29/07, Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
> 1. Scheduling fairness.
> Since kernel does not know about multiple threads behind given process,
> it can not add it appropriate number of timeslices for execution.
> Can be solved either by more tight collaboarion of the userspace and
> kernelspace schedulers or simply by increasing process' nice value.
nice value is only meaningful for SCHED_OTHER. How will you handle a
multithreaded realtime application that uses SCHED_OTHER as well as
SCHED_FIFO threads?
Lee
next prev parent reply other threads:[~2007-02-01 4:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-29 14:52 Evgeniy Polyakov
2007-01-29 14:57 ` Evgeniy Polyakov
2007-01-29 16:40 ` Chris Friesen
2007-01-30 9:46 ` Evgeniy Polyakov
[not found] ` <40f323d00701290747y68c8e27ege824694bfa378f58@mail.gmail.com>
2007-01-30 1:18 ` Samuel Thibault
2007-01-30 9:53 ` Evgeniy Polyakov
2007-01-30 10:24 ` Samuel Thibault
2007-01-30 10:43 ` Evgeniy Polyakov
2007-02-01 4:28 ` Lee Revell [this message]
2007-02-01 7:09 ` Evgeniy Polyakov
2007-01-30 21:16 Kaz Kylheku
2007-01-31 8:47 ` Evgeniy Polyakov
2007-02-02 16:12 ` Bill Davidsen
2007-02-03 15:26 ` Arjan van de Ven
2007-02-04 20:12 ` Bill Davidsen
2007-02-04 20:20 ` Jakub Jelinek
2007-02-04 21:42 ` Bill Davidsen
2007-02-05 6:14 ` Arjan van de Ven
2007-02-14 12:17 ` Pavel Machek
2007-02-04 22:52 ` Davide Libenzi
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=75b66ecd0701312028w7866c608hbf70593055c92b19@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=johnpol@2ka.mipt.ru \
--cc=libc-alpha@sources.redhat.com \
--cc=libc-hacker@sources.redhat.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®