Date: Mon, 27 Aug 2001 19:05:04 -0400 From: Bosko Milekic <bmilekic@technokratis.com> To: Julian Elischer <julian@elischer.org> Cc: Poul-Henning Kamp <phk@critter.freebsd.dk>, Peter Wemm <peter@wemm.org>, Robert Watson <rwatson@FreeBSD.ORG>, current@FreeBSD.ORG Subject: Re: KSE kernel comparissons Message-ID: <20010827190504.A8647@technokratis.com> In-Reply-To: <Pine.BSF.4.21.0108271509190.74870-100000@InterJet.elischer.org>; from julian@elischer.org on Mon, Aug 27, 2001 at 03:09:53PM -0700 References: <69957.998948345@critter> <Pine.BSF.4.21.0108271509190.74870-100000@InterJet.elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 27, 2001 at 03:09:53PM -0700, Julian Elischer wrote: > On Mon, 27 Aug 2001, Poul-Henning Kamp wrote: > > > In message <20010827204331.83656390B@overcee.netplex.com.au>, Peter Wemm writes: > > > > >My personal check list before committing it to -current is: > > >- an honest shot at getting the Alpha working. Shouldn't be too hard. > > > I'll work on this if nobody else will. > > >- finish the userland build stuff. > > >- carefully reread all of the key diffs for i386/i386/*, kern/*, vm/* etc. > > >- take a look at ports impact and prepare them for the landing. > > > > If you add: > > > > - Beat the shit out of it together with other developers for a couple of > > weeks. > > > > Then I'm all for committing it when you have checked off those boxes. > > I agree with this list. I think that realistically speaking, after having looked over the diff, and after considering what was discussed here, that it would be a good time to introduce the KSE work done thus far some time soon, after said testing is done. The reason for this is that the KSE changes to date are, as Julian and some others mentionned, "infrastructural changes," and not _functional_ changes. Therefore, I don't expect them to create additional logic issues (e.g. "I wonder if it's KSE's semantics that are breaking this..." shouldn't come up with these changes when debugging other code). Thus, I agree with Peter and Julian on this issue and will be applying the diff to both dual CPU machines I have here and testing tonight. At the same time, I do hope that the actual _functional_ changes come in a hopefully more orderly/slower manner so that it is in fact possible to track down logic problems w.r.t. KSE should they arise. On another (perhaps unrelated) note, I've noticed on the lists at least one or two -CURRENT users/testers insist on having KSE functionality but at the same time expecting to have production material in early 5.0 "releases." I find this to be disturbing. While I do agree that earlier "5.0 releases" should deffinately reach out to the largest userbase possible, I am concerned that some users will perhaps expect so much from the system that they will immediately go ahead and pit it against more mature SMP OSes out there and then go on to complain about everything under the Sun because "brand new functionality (X) is not what I expected." The robustness and performance of the work being done now will become more and more apparent only as things progress and it should be noted that all of these "nice things" resulting from all the work we're presently doing will not just all magically surface when 5.0-RC1 (or whatever it's going to be called) is "released." -- Bosko Milekic bmilekic@technokratis.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010827190504.A8647>