diff options
| author | Kimplul <kimi.h.kuparinen@gmail.com> | 2021-12-30 20:48:26 +0200 |
|---|---|---|
| committer | Kimplul <kimi.h.kuparinen@gmail.com> | 2021-12-30 20:48:26 +0200 |
| commit | 6f052e236715846b1a14f9fe59f89346efb809e6 (patch) | |
| tree | c1bbca5a063c428f65c46b34aaf4dbf47e61c213 /TODO.txt | |
| parent | 4f4d9fdc89c27aa3346467a24b621954f4564d3b (diff) | |
| download | kmi-6f052e236715846b1a14f9fe59f89346efb809e6.tar.gz kmi-6f052e236715846b1a14f9fe59f89346efb809e6.zip | |
Add initial version of device memory mapping
Diffstat (limited to 'TODO.txt')
| -rw-r--r-- | TODO.txt | 10 |
1 files changed, 10 insertions, 0 deletions
@@ -19,3 +19,13 @@ well + check elf.c "skip while testing" comment, remove when sufficiently pleased with the system. Christ, what a terrible way to develop software :D + Start working on syscalls etc. + ++ NUMA is probably fairly easy to setup, just add more pmaps I guess, although +it does sort of mess with the current device memory setup, which assumes there +is only one memory region and everything below/above it is device memory +regions. Not entirely sure how to handle that situation, i.e. is it safe to +assume all devices are below the first NUMA node? No clue. + ++ The dev interface can be abused, if a program decides to spam through all +memory addresses the system will probably run out of memory. Not sure if it's +worh doing anything to. |