I'm surprised. ext2's fsync in 2.2 is in fact quite optimal: a single
pass across the block tree, in probable-LBA-order. No livelock potential
there. Optimal. Note that it implements "only sync the stuff which was
dirty on entry" semantics.
But msync() is a different kettle of fish. It calls file_fsync(), which
syncs the entire device, livelockably. Are you sure `solid' is not
using msync?
-
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/