linux-kernel - Re: modifying CFS failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Sun, 13 Apr 2008 21:23:00 +0530 (IST)
From:	cs044024@...it.ac.in
To:	linux-kernel@...r.kernel.org
Cc:	"Willy Tarreau"@mnnit.ac.in, " <w@....eu>, "@mnnit.ac.in,
	Peter@...it.ac.in, Zijlstra@...it.ac.in,
	" <peterz@...radead.org>"@mnnit.ac.in
Subject: Re: modifying CFS failure

> 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.


--
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/