* Poul-Henning Kamp <[EMAIL PROTECTED]> [010424 08:36] wrote:
> In message <[EMAIL PROTECTED]>, Garrett Wollman write
> s:
> ><<On Mon, 23 Apr 2001 21:51:31 -0700, Alfred Perlstein <[EMAIL PROTECTED]> said:
> >
> >> You can find the work I've done so far to make a giant vm mutex
> >> here:
> >
> >The Mach code we originally inherited was supposed to already by
> >multiprocessor safe. Did we manage to eliminate that capability?
>
> I'm sure you are fully aware of the implications of the strategically
> placed "supposed" in your own sentence. I have never heard anybody
> get Mach code multithreaded yet.
It's not just that, looking at the old code it doesn't seem to deal
very well actually performing the IO, there's also other issues
that Alan Cox and Matt Dillon explained to me where in certain
locations vm_object lists are traversed in forward and reverse
order, this causes a lock order problem, it could be fixed by
possibly sharing a lock across object chains, but for now moving
to a giant lock is still a step in the right direction because
as I've mentioned, with everything still under Giant we've still
got decent performance.
--
-Alfred Perlstein - [[EMAIL PROTECTED]]
Instead of asking why a piece of software is using "1970s technology,"
start asking why software is ignoring 30 years of accumulated wisdom.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
