linux-kernel - Re: [PATCH 3/3] Subject: SCHED - Use a 2-d bitmap for searching lowest-pri CPU

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20071205114438.GC6143@elte.hu>
Date:	Wed, 5 Dec 2007 12:44:38 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Gregory Haskins <ghaskins@...ell.com>
Cc:	rostedt@...dmis.org, linux-kernel@...r.kernel.org,
	linux-rt-users@...r.kernel.org
Subject: Re: [PATCH 3/3] Subject: SCHED - Use a 2-d bitmap for searching
	lowest-pri CPU

* Gregory Haskins <ghaskins@...ell.com> wrote:

> However, that said, Steven's testing work on the mainline port of our 
> series sums it up very nicely, so I will present that in lieu of 
> digging up my -rt numbers unless you specifically want them too.  Here 
> they are:

i'm well aware of Steve's benchmarking efforts, but i dont think he's 
finished with it and i'll let him present the results once he wants to 
announce them. I asked about the effects of the "2-d" patch in isolation 
and i'm not sure the numbers show that individual patch in action.

in any case, you are preaching to the choir, i wrote the first 
rt-overload code and it's been in -rt forever so it's not like you need 
to sell me the concept ;-) But upstream quality requirements are 
different from -rt and we need to examine all aspects of scheduling, not 
just latency. In any case, i'll wait for the rest of Steve's numbers.

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