From: cs044024@mnnit.ac.in
To: linux-kernel@vger.kernel.org
Cc: "Willy Tarreau"@mnnit.ac.in, " <w@1wt.eu>,
"@mnnit.ac.in, Peter@mnnit.ac.in, Zijlstra@mnnit.ac.in,
" <peterz@infradead.org>"@mnnit.ac.in
Subject: Re: modifying CFS failure
Date: Sun, 13 Apr 2008 21:23:00 +0530 (IST) [thread overview]
Message-ID: <43702.210.212.49.15.1208101980.squirrel@mail.mnnit.ac.in> (raw)
In-Reply-To: <1208002923.7427.5.camel@twins>
> 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.
>
We haven't modified anything in CFS except replacing all the RB-Tree
function calls by AVL tree function calls, so that only the implementation
of the tree DS changes, and everything else remains same. We have retained
the interface of tree DS and core scheduler as it is, so we assumed that
everything must work fine.
> 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.
>
Actually we wanted to replace RB with time ordered radix tree. But that
seemed a tougher task, so we started with AVL trees first.
> I'm glad people are working on CFS - its an interesting piece of the
> kernel after all...
>
Thanks. This is really encouraging.
prev parent reply other threads:[~2008-04-13 15:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-12 3:46 cs044024
2008-04-12 12:22 ` Peter Zijlstra
2008-04-12 13:22 ` Willy Tarreau
2008-04-13 15:53 ` cs044024 [this message]
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=43702.210.212.49.15.1208101980.squirrel@mail.mnnit.ac.in \
--to=cs044024@mnnit.ac.in \
--cc=" <peterz@infradead.org>"@mnnit.ac.in \
--cc=" <w@1wt.eu>, "@mnnit.ac.in \
--cc="Willy Tarreau"@mnnit.ac.in \
--cc=Peter@mnnit.ac.in \
--cc=Zijlstra@mnnit.ac.in \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®