mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jacques Gelinas <jack@solucorp.qc.ca>
To: Linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Announce: many virtual servers on a single box (scheduling)
Date: Mon, 15 Oct 2001 21:43:31 -0500	[thread overview]
Message-ID: <20011015214331.6cf66bb2bd01@remtk.solucorp.qc.ca> (raw)

On Mon, 15 Oct 2001 17:22:43 -0500, James Sutherland wrote

> Hmmm - does this work with devfs?

Not tried. Sorry. Note that vserver can't mount.

> Have you looked at the "fairsched" patch for this? It seems to be
> unmaintained since 2.4.0-testXX, but look close to your needs...

So far I am toying with a very simple solution. The current schedular (SCHED_OTHER)
is using each process p->counter (time quantum used so far) as one data to
compute the priority.

Security context are sharing a common struct context_info and it contains
a counter too (atomic_t counter). When the process p->counter is decremented
the context_info->counter is also decremented. This context_info counter is
used along with the p->counter to compute the process priority. So if a vserver
is running many processe, then their total cpu usage is accounted in their
common context_info->counter, so they have lover priority (together) than
a single process in another vserver.

Note that this idea is broad. A PAM module could be use to setup a per-user
context_info, without switching the security ID and you end up with
per-user fair schedular (well, per whatever).

Note also that this per context_info scheduling is a flag (you can only turn it on).
By default, there is no special scheduling in a vserver.

---------------------------------------------------------
Jacques Gelinas <jack@solucorp.qc.ca>
vserver: run general purpose virtual servers on one box, full speed!
http://www.solucorp.qc.ca/miscprj/s_context.hc

                 reply	other threads:[~2001-10-16  3:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20011015214331.6cf66bb2bd01@remtk.solucorp.qc.ca \
    --to=jack@solucorp.qc.ca \
    --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®