public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: Peter Zijlstra <peterz@infradead.org>
Cc: cs044024@mnnit.ac.in, linux-kernel@vger.kernel.org,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: modifying CFS failure
Date: Sat, 12 Apr 2008 15:22:35 +0200	[thread overview]
Message-ID: <20080412132235.GC8474@1wt.eu> (raw)
In-Reply-To: <1208002923.7427.5.camel@twins>

On Sat, Apr 12, 2008 at 02:22:03PM +0200, Peter Zijlstra wrote:
> Please provide it as a series of patches against sched-devel/latest.
> 
> Just plain AVL code and a huge modified CFS backport make it impossible
> to tell what changed and why.
> 
> Which brings us to the question: _why_. That is, why are you trying to
> replace the rb-tree with an avl tree? Just because the worst case depth
> of the avl is slightly better than for an rb-tree, which can be offset
> by the slightl more expesive balance operations.

I would add that in the past, I too tried to replace the rbtree in order
to provide O(1) node deletion time. The tree was not balanced at all
(which provided faster operations). But the net result was very small
(maybe 1%, I don't remember exactly). The reason was that in practise,
the CFS rbtree does not change *that* often, and the pointer to the
first node already provides a great boost. I remember I had to play
in the area of millions of context-switches/s to see a difference, so
it was quite pointless (though the exercise itself was interesting).

> I'm glad people are working on CFS - its an interesting piece of the
> kernel after all, but provide it in a regular patch series, this is
> impossible to work with, sorry.

agreed.

Willy


  reply	other threads:[~2008-04-12 13:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-12  3:46 modifying CFS failure cs044024
2008-04-12 12:22 ` Peter Zijlstra
2008-04-12 13:22   ` Willy Tarreau [this message]
2008-04-13 15:53   ` cs044024

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=20080412132235.GC8474@1wt.eu \
    --to=w@1wt.eu \
    --cc=cs044024@mnnit.ac.in \
    --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