Re: [openbeos] Re: GSoC ticket #1069 (thread scheduler) application

On 4/11/07, Ingo Weinhold <bonefish-CFLBMwTPW48UNGrzBIF7/[email protected]> wrote:
> We're planing to have a slab allocator for our kernel anyway. If your
> stuctures end up being small enough (i.e. smaller than a cache line; in case
> of per-thread data you'd obviously have to separate them from struct thread
> then) you can simply use a separate cache, which will result in exactly the
> locality you're looking for.

I have to separate them already, since I can't break binary
compatibility with struct thread. This second approach is what I meant
all along, actually. That, and a clever algorithm to allocate "alike"
threads together.

> I don't think it's usually more than a few hundred threads. I'd be surprised,
> if I ever managed to have more than 1000 threads at the same time. The hard
> limit under BeOS is 4096; IMHO completely sufficient.

Understood.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV