[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <DD13278E-1E04-46D2-88E0-14A8B002CD90@mac.com>
Date: Tue, 13 Mar 2007 00:17:35 -0400
From: Kyle Moffett <mrmacman_g4@....com>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Mike Galbraith <efault@....de>, Con Kolivas <kernel@...ivas.org>,
Ingo Molnar <mingo@...e.hu>,
linux kernel mailing list <linux-kernel@...r.kernel.org>,
ck list <ck@....kolivas.org>,
Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [PATCH][RSDL-mm 0/7] RSDL cpu scheduler for 2.6.21-rc3-mm2
On Mar 12, 2007, at 11:26:25, Linus Torvalds wrote:
> So "good fairness" really should involve some notion of "work done
> for others". It's just not very easy to do..
Maybe extend UNIX sockets to add another passable object type vis-a-
vis SCM_RIGHTS, except in this case "SCM_CPUTIME". You call
SCM_CPUTIME with a time value in monotonic real-time nanoseconds
(duration) and a value out of 100 indicating what percentage of your
timeslices to give to the process (for the specified duration). The
receiving process would be informed of the estimated total number of
nanoseconds of timeslice that it will be given based on the priority
of the processes. (Maybe it could prioritize requests?). The X
libraries could then properly "pass" CPU time to the X server to help
with rendering their requests, and the X server could give priority
to tasks which give up more CPU time than is needed to render their
data, and penalize those which use more than they give. Initially
even if you don't patch the X server you could at least patch the X
clients to give up CPU to the X server to promote interactivity.
Cheers,
Kyle Moffett
-
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