Re: cvs commit: src/sys/conf files src/sys/i386/i386 machdep.c src/sys/kern init_sysent.c kern_usched.c syscalls.c syscalls.master usched_bsd4.c src/sys/sys syscall-args syscall-hide.h syscall.h syscall.mk sysproto.h sysunion.h usched.h

[Oliver Fromme <check+iq5p4z00rsyiwodu@xxxxxxxxxx>]

Sergey Glushchenko <deen@xxxxxxxxxx> wrote:
 > [...]  The second step will be mechanism that makes several 
 > schedulers co-exist with each other. Then we will have complete 
 > usched framework and it would be possible to write new schedulers
 > if desired.

I have a (maybe) dumb question, just out of curiosity ...

When there are multiple schedulers, how will resources
(i.e. processor time) be shared between them?  Will there
be a "meta scheduler" which assigns processor time to the
various schedulers, which in turn assign it to processes?

And anther question:  Will it be possible to migrate
running processes from one scheduler to a different one?

And how is this different from the concept of scheduling
classes, like in Solaris?  Or is it just the same?

Best regards
   Oliver

-- 
Oliver Fromme,  secnetix GmbH & Co. KG, Marktplatz 29, 85567 Grafing
Dienstleistungen mit Schwerpunkt FreeBSD: http://www.secnetix.de/bsd

Any opinions expressed in this message may be personal to the author
and may not necessarily reflect the opinions of secnetix in any way.