From: Gustavo Homem <gustavo@angulosolido.pt>
To: linux-kernel@vger.kernel.org
Subject: CONFIG_FAIR_USER_SCHED oficial replacement
Date: Sat, 26 Oct 2013 02:55:04 +0100 (WEST) [thread overview]
Message-ID: <650686eb-3310-41cd-9547-b4604ef78380@mailserver01.multibase.pt> (raw)
In-Reply-To: <4fe6af83-0c8b-41d7-87b5-2beee3402632@mailserver01.multibase.pt>
Hi,
I've been reading documentation on fair share scheduling and apparently the CONFIG_FAIR_USER_SCHED option has been removed from the kernel. If I understood correctly the use of this option would automatically enable per user fair share scheduling, with each user's processes falling directly into the right schedule group.
Question: what is currently the recommended way of achieving the same effect? I understand that there is a general approach for task groups, but on a multi-user environment with a varying number of users it is not clear to me what is the preferred method for automatically creating and removing the groups and distributing the processes to each group.
Best regards
Gustavo
--
Angulo Sólido - Tecnologias de Informação
http://angulosolido.pt
parent reply other threads:[~2013-10-26 2:05 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <4fe6af83-0c8b-41d7-87b5-2beee3402632@mailserver01.multibase.pt>]
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=650686eb-3310-41cd-9547-b4604ef78380@mailserver01.multibase.pt \
--to=gustavo@angulosolido.pt \
--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®