Re: amd64 cpu_switch in C.

On Tue, Mar 11, 2008 at 3:02 AM, Poul-Henning Kamp <phk@xxxxxxxxxxxxxx> wrote:
In message <20080311095557.GX68971@xxxxxxxxxxxxxxxxxxxxxxx>, Peter Jeremy write
s:


>>The only appreciable downside is that it lowers the barrier of entry for
>>modifying a very sensitive piece of code.
>
>IMHO, this isn't a valid reason. Increasing the both the legibility
>and performance of a very sensitive piece of code is a good thing.
>Having more people understand the code is also a good thing.

This is not a legal inference, and that's exactly the point Jeff made:

Just because it is written in C doesn't mean people will understand
it, it merely means that they will _think_ they understand it.

I'd like to point out that if I hadn't converted the run queue parts
of cpu_switch into C, then KSE might never have happened. At least,
not in the form that hit the tree.

--
Peter Wemm - peter@xxxxxxxx; peter@xxxxxxxxxxx; peter@xxxxxxxxxxxxx
"All of this is for nothing if we don't go to the stars" - JMS/B5
"If Java had true garbage collection, most programs would delete
themselves upon execution." -- Robert Sewell
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"

Relevant Pages
Quantcast