From: "Chris Friesen" <cfriesen@nortel.com>
To: vatsa@in.ibm.com
Cc: riel@redhat.com, Ingo Molnar <mingo@elte.hu>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC] Fair-user scheduler
Date: Fri, 26 Jan 2007 12:41:27 -0600 [thread overview]
Message-ID: <45BA4B57.1070604@nortel.com> (raw)
In-Reply-To: <20070126060142.GA2487@in.ibm.com>
Srivatsa Vaddagiri wrote:
> Current Linux CPU scheduler doesnt recognize process aggregates while
> allocating bandwidth. As a result of this, an user could simply spawn large
> number of processes and get more bandwidth than others.
>
> Here's a patch that provides fair allocation for all users in a system.
>
> Some benchmark numbers with and without the patch applied follows:
>
>
> user "vatsa" user "guest"
> (make -s -j4 bzImage) (make -s -j20 bzImage)
>
> 2.6.20-rc5 472.07s (real) 257.48s (real)
> 2.6.20-rc5+fairsched 766.74s (real) 766.73s (real)
As Kirill brought up, why does it take so much more time? Are you
thrashing the cache?
> - breaks O(1) (ouch!)
> Best way to avoid this is to split runqueue to be per-user and
> per-cpu, which I have not implemented to keep the patch simple.
Presumably this would be made generic, as in per-"group" rather than per
user?
> - Fairsched aware SMP load balance NOT addressed (yet)
This is kind of important, no?
Chris
next prev parent reply other threads:[~2007-01-26 18:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 6:01 [RFC] Fair-user scheduler Srivatsa Vaddagiri
2007-01-26 6:03 ` [PATCH 1/2] core scheduler changes Srivatsa Vaddagiri
2007-01-31 15:01 ` Srivatsa Vaddagiri
2007-01-26 6:05 ` [PATCH 2/2] Track number of users in the system Srivatsa Vaddagiri
2007-01-26 14:09 ` [RFC] Fair-user scheduler Kirill Korotaev
2007-01-26 18:52 ` Eric Piel
2007-01-31 15:10 ` Srivatsa Vaddagiri
2007-01-26 18:41 ` Chris Friesen [this message]
2007-01-31 15:16 ` Srivatsa Vaddagiri
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=45BA4B57.1070604@nortel.com \
--to=cfriesen@nortel.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=riel@redhat.com \
--cc=vatsa@in.ibm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.