[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45FCFC28.6030701@argo.co.il>
Date: Sun, 18 Mar 2007 10:45:28 +0200
From: Avi Kivity <avi@...o.co.il>
To: Willy Tarreau <w@....eu>
CC: Radoslaw Szkodzinski <astralstorm@...il.com>,
linux-kernel@...r.kernel.org, Al Boldi <a1426z@...ab.com>,
Andrew Morton <akpm@...ux-foundation.org>,
William Lee Irwin III <wli@...omorphy.com>,
ck@....kolivas.org, Linus Torvalds <torvalds@...ux-foundation.org>,
Nicholas Miell <nmiell@...cast.net>
Subject: Re: [ck] Re: is RSDL an "unfair" scheduler too?
Willy Tarreau wrote:
>> The per-user system would also be nice for servers, provided there are
>> CPU/disc IO/swapper/... quotas or priorities at least.
>>
>
> This is too hard to adjust. Imagine what would happen to your hundreds of
> apache processes when the "backup" user will start the rsync or tar+gzip,
> or when user "root" will start rotating and compressing the logs. Being
> able to group processes may be useful on servers, but it should be enabled
> on purpose by the admin.
>
Sure, if implemented, it should default to the old behavior to avoid
surprises. Maintenance jobs may have to be niced to avoid getting too
much cpu. But it should also make hosting different applications on the
the server much more predictable and easier (think of your hundreds of
apache processes swamping an unrelated load when slashdotted).
--
error compiling committee.c: too many arguments to function
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists