> > Maybe in the allocator you skip otherwise free blocks if they intersect > > with the run time structure (rbtree of extents, presumably) that is > > taking the place of reference counts in struct page. There aren't > > *that* many allocator entry points. I guess you'd need to avoid other > > modifications of free space like trimming :/. It still seems reasonably > > doable? > > Ah, so on reboot, the on-disk data structures are all correct, and > the in-memory data structures went away with the runtime pinning of > the memory. Nice. Yeah, that's what I was picturing. The part I'm most fuzzy on is how to get current g_u_p() callers consuming the mappings without full struct pages. - z -- To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
