Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 29 Jan 2003 04:20:02 -0500 (EST)
From:      Jeff Roberson <jroberson@chesapeake.net>
To:        Kris Kennaway <kris@obsecurity.org>
Cc:        Julian Elischer <julian@elischer.org>, <arch@FreeBSD.ORG>
Subject:   Re: threads and the scheduler(s).
Message-ID:  <20030129041155.Y31308-100000@mail.chesapeake.net>
In-Reply-To: <20030128201901.A1673@citusc.usc.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
>
> I'm kind of concerned that KSE has turned into something much more
> complicated than it should ever have been (and already was at the
> beginning).  I understand scheduler activations, but as far as I can
> tell we're no longer even close to the original KSE design because of
> various incremental changes in direction, and there's no coherent
> documentation for the current state of affairs (or explanations for
> the various design decisions in departure from the original design).
>
> I guess I don't actually have anything constructive to say, but I
> really hope this whole KSE thing isn't going to turn out to be an
> over-designed way of not-really-solving non-problems.
>

I had many of these same concerns as I began to work on ule.  After
thinking hard about the problem and how I might attack it, I eventually
decided that this is the right way.  A long conversation with mini on IRC
one night actually got me to start liking it.  I think I came at it with
the same perspective that many in the project have.  I had a reasonable
understanding of SA and LPWs but this didn't make much sense.  I think a
design doc, or at the very least a description of how and why this differs
from traditional SA, would go a long way towards settling peoples fears
about KSE.  I think it's just not well understood by many.

My concerns now are mostly with how long it will take before it works and
how long it will take before it works well.  It is a complicated system.
There are too few people working on it.  It's also a major sore spot for
FreeBSD to not have it.

Cheers,
Jeff


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030129041155.Y31308-100000>