public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Michael Trimarchi <trimarchi@gandalf.sssup.it>
To: sat <takeuchi_satoru@jp.fujitsu.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
	Con Kolivas <kernel@kolivas.org>, Ingo Molnar <mingo@elte.hu>,
	Peter Zijlstra <peterz@infradead.org>,
	Raistlin <raistlin@linux.it>
Subject: Re: massive_intr on CFS, BFS, and EDF
Date: Fri, 25 Sep 2009 18:07:24 +0200	[thread overview]
Message-ID: <4ABCEABC.4050200@gandalf.sssup.it> (raw)
In-Reply-To: <4ABC068A.6070704@jp.fujitsu.com>

Hi,
sat wrote:
> Hi,
>
> I tried massive_intr, a process scheduler's fairness and throughtput testing
> program for massive interactive processes, on vanilla 2.6.31, 2.6.31-bfs211
> (with BFS) and 2.6.31-edf(latest linus tree + EDF patch).
>
> CFS and BFS look good. CFS has better fairness, and BFS has better throughput.
> EDF looks unfair and is unstable. I tested 3 times and the tendency was the
> same.
Thank you for your testing, the instability problems you hit are due to
some bugs in our implementation, we'll try to reproduce and fix them.
Your test shows that we have some problems with how we handle fork();
the code attempts at distributing the bandwidth between the parent and
the child, and the fact that the children hang means that there is
something wrong in how we handle recharges. It is important to note that
the expected behavior of an edf scheduler is *not* a fair one. It has to
do its best to guarantee the deadlines of the admitted tasks.

Regards Michael

  parent reply	other threads:[~2009-09-25 17:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-24 23:53 massive_intr on CFS, BFS, and EDF sat
2009-09-25  3:27 ` Satoru Takeuchi
2009-09-25  5:35   ` Raistlin
2009-09-25  5:35 ` Raistlin
2009-09-25 16:07 ` Michael Trimarchi [this message]
2009-09-25 21:31   ` Chris Friesen
2009-09-25 22:37     ` Peter Zijlstra
2009-09-25 22:46       ` Chris Friesen
2009-09-26  7:22         ` Raistlin
2009-09-26  6:56       ` Raistlin
2009-09-26  6:50     ` Raistlin

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=4ABCEABC.4050200@gandalf.sssup.it \
    --to=trimarchi@gandalf.sssup.it \
    --cc=kernel@kolivas.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=raistlin@linux.it \
    --cc=takeuchi_satoru@jp.fujitsu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox