From: William Pitcock <nenolod@dereferenced.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Mike Galbraith <efault@gmx.de>
Subject: Re: [PATCH try 3] CFS: Add hierarchical tree-based penalty.
Date: Tue, 12 Oct 2010 14:02:56 +0400 (MSD) [thread overview]
Message-ID: <87939.1771286877776896.JavaMail.root@ifrit.dereferenced.org> (raw)
In-Reply-To: <31330936.1751286877737150.JavaMail.root@ifrit.dereferenced.org>
Hi,
----- "Peter Zijlstra" <peterz@infradead.org> wrote:
> On Tue, 2010-10-12 at 13:34 +0400, William Pitcock wrote:
> > Yes, this should be a multiplication I believe, not a divide. My
> original
> > code had this as a multiplication, not a division, as does the new
> patch.
> >
> > However, I think:
> >
> > vruntime >>= tsk->fork_depth;
> >
> > would do the job just as well and be faster.
>
> That's still somewhat iffy as explained, vruntime is the absolute
> service level, multiplying that by 2 (or even more) will utterly
> upset
> things.
>
Yes, this is why I thought that doing a division would be better.
> Imagine two runnable tasks of weight 1, say both have a vruntime of 3
> million, seconds (there being two, vruntime will advance at 1/2
> wall-time).
>
> Now, suppose you wake a third, it too had a vruntime of around 3
> million
> seconds (it only slept for a little while), if you then multiply that
> with 2 and place it at 6 mil, it will have to wait for 6 mil seconds
> before it gets serviced (twice the time of the 3 mil difference in
> service time between this new and the old tasks).
>
> So, theory says the fair thing to do is place new tasks at the
> weighted
> average of the existing tasks, but computing that is expensive, so
> what
> we do is place it somewhere near the leftmost task in the tree.
>
> Now, you don't want to push it out too far to the right, otherwise we
> get starvation issues and people get upset.
>
> So you have to somehow determine a window in which you want to place
> this task and then vary in that depending on your fork_depth.
>
> Simply manipulating the absolute service levels like you propose
> isn't
> going to work.
I think I have a solution to this. Presently waiting on a kernel rebuild
on my laptop so I can test.
William
next parent reply other threads:[~2010-10-12 10:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <31330936.1751286877737150.JavaMail.root@ifrit.dereferenced.org>
2010-10-12 10:02 ` William Pitcock [this message]
[not found] <29349823.1671286875856124.JavaMail.root@ifrit.dereferenced.org>
2010-10-12 9:34 ` [PATCH try 3] CFS: Add hierarchical tree-based penalty William Pitcock
2010-10-12 9:46 ` Peter Zijlstra
2010-10-12 5:32 William Pitcock
2010-10-12 8:45 ` Peter Zijlstra
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=87939.1771286877776896.JavaMail.root@ifrit.dereferenced.org \
--to=nenolod@dereferenced.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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