![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
pphaneufA bit of a technical post, since my other diary is currently broken (yay for computers).
Reiserfs is terrible. I don't know much about the design, but the style of the code leaves much to be desired.
You remember how doing fread() and fwrite() of structures to disk is a bad idea? Well, that's exactly how the reiserfs superblock is written, including a bunch of pointer members. Wow, stylin'.
The journal flushing algorithm is recursive. Recursive. In the kernel. It has a 4k stack now. Running out of stack will make it panic. Hope you don't have too many transaction piling up between two scheduling of the reiserfs journal flushing thread (people who know me also know what I think of threads).
Is this serious? Jebus, I need a drink.
Reiserfs is terrible. I don't know much about the design, but the style of the code leaves much to be desired.
You remember how doing fread() and fwrite() of structures to disk is a bad idea? Well, that's exactly how the reiserfs superblock is written, including a bunch of pointer members. Wow, stylin'.
The journal flushing algorithm is recursive. Recursive. In the kernel. It has a 4k stack now. Running out of stack will make it panic. Hope you don't have too many transaction piling up between two scheduling of the reiserfs journal flushing thread (people who know me also know what I think of threads).
Is this serious? Jebus, I need a drink.
