4 ms·
> Stay tuned for multiprocessor support! The dump below that statement appears to verify that only one of the 4 cores is operational. I'm surprised that multi
by mark-r 12y ago
> Stay tuned for multiprocessor support!
The dump below that statement appears to verify that only one of the 4 cores is operational.
I'm surprised that multiprocessor support would be a big deal to implement.
- bch 12y agoThis is _not_ the official repo[1], but I can't resist showing off how excellent fossil[2] is. This fossil repo[3] of Jörg[4] (notable NetBSD (and fossil) developer) mirrors the CVS repo - watch the development, or trawl the code yourself to see what's going on. Enjoy. [1] http://cvsweb.netbsd.org/bsdweb.cgi/ http://cvsweb.netbsd.org/bsdweb.cgi/ [2] http://www.fossil-scm.org http://www.fossil-scm.org [3] http://netbsd.sonnenberger.org http://netbsd.sonnenberger.org [4] http://www.sonnenberger.org/ http://www.sonnenberger.org/
- morganvachon 12y agoI don't know the technical reasons behind it, but both OpenBSD and NetBSD once had issues with SMP. I think they both have resolved them in x86 land but I don't know about other platforms. Maybe this is a similar issue and won't take long to work out.
- bch 12y agoNetBSD has had multiprocessor support since 2004 [1] -- the biggest thing I remember re: "multi" support was fiddling w/ the thread model, which was a sort of radical period in development[2]... [1] http://en.wikipedia.org/wiki/NetBSD#Symmetric_multiprocessing http://en.wikipedia.org/wiki/NetBSD#Symmetric_multiprocessin... [2] http://en.wikipedia.org/wiki/Scheduler_activations http://en.wikipedia.org/wiki/Scheduler_activations
- justincormack 12y agoWell doing everything at once is not necessary, I don't suppose it will take long, but its always good to test as you go.