Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

raw disk #337

Open
boogerlad opened this issue Jan 27, 2022 · 2 comments
Open

raw disk #337

boogerlad opened this issue Jan 27, 2022 · 2 comments

Comments

@boogerlad
Copy link

I see Project:M36 currently saves its state in memory or to a file. I don't know how hard it would be, but it would be nice to use an Intel 3D XPoint or some other sort of fast non volatile memory directly. Possibly better performance due to being able to optimize further, and operating system independent. This would also solve the chicken and the egg problem of new operating systems without hierarchical file systems.
@agentm
Copy link
Owner

agentm commented Jan 27, 2022

Indeed, I am excited about new storage technologies as well. Project:M36 has a bunch of low-hanging fruit to implement in this context. I hope that you have seen "UltraRAM" as well. It's not immediately clear, at least to me, how/when the operating system will discern between temporary and permanent storage and the current APIs will probably not suffice, so I'm keeping an eye on this.

@agentm
Copy link
Owner

agentm commented Oct 3, 2022

Note that Project:M36 currently uses essential and common file system features:

  • journaled fs metadata- enables durability of ACID
  • fsync/fdatasync- enables durability of ACID
  • parallel writing to disk

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@agentm @boogerlad