Quote:
Originally Posted by ibara
Which ones?
|
I quickly grabbed a few blurbs of text from
Wikipedia and the
Dragonfly Features page:
In DragonFly, each CPU has its own thread scheduler. Upon creation, threads are assigned to processors and are never preemptively switched from one processor to another
PROCESS CHECKPOINTING
Processes under DragonFly may be "checkpointed" or suspended to disk at any time. They may later be resumed on the originating system, or another system by "thawing" them.
Application snapshots
DragonFly BSD supports Amiga-style resident applications feature: it takes a snapshot of a large, dynamically linked program's virtual memory space after loading, allowing future instances of the program to start much more quickly than it otherwise would have.
Quote:
Originally Posted by ibara
Why?
|
I've been thinking about a light-weight cluster architecture.
5.7 system freeze - reproducible (post #6)
VKERNEL might also be useful, and/or maybe D-Trace (though, I haven't really thought about the implications). Could be very helpful when there are problems.
Tor-0.2.5.12 can crash OpenBSD-5.7-stable (post #3)