On Mon, Feb 16, 2026 at 3:45 AM Alyssa M via 9fans <[email protected]> wrote: > > This is interesting because it's a large data structure that's very sparsely > read or written. I'd read the entire file system image into the segment in > one gulp, respond to some file protocol requests (e.g. over 9P) by treating > the segment as a single data structure, and write the entire image out > periodically to implement what we used to call 'sync'. > With traditional I/O that would be ridiculous. With the above mechanism it > should work about as well as mmap would. And without all that cache code and > block fetching. Which is the point of this.
"I'd read the entire file system image into the segment in one gulp" But you wouldn't, actually, as you already aluded to... Are you aware how read() is commonly implemented? Maybe you get confused between kernelspace and userspace? Where is this fileserver running for you? In kernel or not? ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Te8d7c6e48b5c075b-Mb5da462dfb5824b832ee4d7f Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
