Linked by Thom Holwerda on Sat 24th Feb 2007 21:25 UTC, submitted by mdoverkil
BSD and Darwin derivatives Apparently, Matt Dillion has decided to roll his own filesystem for DragonFly. "Here is my initial outline of the filesystem design. It is open for discussion. Please feel to ask questions for anything you do not understand. I do not intend to start coding anything for at least two weeks. There are currently two rough spots in the design. First, how to handle segment overflows in a multi-master environment. Such overflows can occur when the individual masters or slaves have different historical data retention policies. Second, where to store the regeneratable indexes."
Permalink for comment 216315
To read all comments associated with this story, please click here.
RE: Find a niche for Dragonfly
by butters on Sun 25th Feb 2007 05:45 UTC in reply to "Find a niche for Dragonfly "
Member since:

They are NOT positioning DragonFly as a general purpose OS. They are instead designing an multi-node clustering OS that scales in number of nodes without impacting the overhead of maintaining cache coherency across nodes. It is also suitable for single-node systems (i.e. with only one cache coherency domain), but this is merely a degenerate case of the general design.

DragonFly is designed primarily with upward scaling in mind. On a single-CPU system, the locks in traditional *nix and the MPI in DragonFly compile away to essentially the same model of process and memory management. In this case, you go with whatever has the best hardware and software support, and that isn't DragonFly.

EDIT: After reading more of this thread, and I totally disappointed with the display of ignorance. Feel free to ask questions if you don't understand what DF is all about, but don't dismiss what they're trying to do if you have absolutely zero clue as to the goals of the project.

Edited 2007-02-25 05:52

Reply Parent Score: 5