diff options
| author | Kimplul <kimi.h.kuparinen@gmail.com> | 2024-07-17 19:29:37 +0300 |
|---|---|---|
| committer | Kimplul <kimi.h.kuparinen@gmail.com> | 2024-07-17 19:29:37 +0300 |
| commit | be82edec47b20164c0e8a9917fa2c9b8b9999fdf (patch) | |
| tree | 79124d9eb60abf2b3736d70c3244c4c5df0f0426 /TODO | |
| parent | 06cd3ac67f9e039219df21d4bf63bf53b666355a (diff) | |
| download | kmi-be82edec47b20164c0e8a9917fa2c9b8b9999fdf.tar.gz kmi-be82edec47b20164c0e8a9917fa2c9b8b9999fdf.zip | |
make compilation more robust on *BSD
Diffstat (limited to 'TODO')
| -rw-r--r-- | TODO | 5 |
1 files changed, 5 insertions, 0 deletions
@@ -52,6 +52,11 @@ associated program. Easy. (started) be visible from cur_tcb() when in an RPC? should I use some kind of effective tid instead of cur_tcb()?) + Export VM flags to userspace, separate header or something? ++ Get core count? It's technically speaking available from the fdt but could be +limited by the NR_CPUS macro, so it might be a good idea to export as a CONF_* ++ The node subsystem might benefit from larger-than-base-page sizes, for example + the RISC-V V extension allows up to 262 144 bytes of register space (though it + seems unlikely that anyone actually uses that many but still) !!! FUTURE: + Cache locality? |
