| Age | Commit message (Collapse) | Author |
|---|
|
The postqueue functions remain as-is, as that's a more "specialized" interface.
They're mostly wrappers around queue.h, though.
|
|
|
|
I'm still not sure if I should use sys/queue.h for this.
But yeah, this is more consistent, and it will also let me switch over to O(1)
insertions later on.
|
|
Keeping its old name for now to make things easier for myself.
This might just be replaced by sys/queue.h soon.
|
|
|
|
The bitmap functions now accept page addresses so I don't have to handle
raw bitmap indexes, which was kinda complex.
kmalloc_sanity is now not visible to other code as it wasn't really that useful
in the first place.
|
|
This will likely be changed back, but for the time being it will let me
implement a better allocator without too much effort.
|
|
To use the same testing methodology as when I've introduced request slots:
before:
/ $ iostress 1 1000000 0 > /dev/vtty
run 0: 2585203
1000000 calls, 0 bytes. avg 2585203
after:
/ $ iostress 1 1000000 0 > /dev/vtty
run 0: 2783171
1000000 calls, 0 bytes. avg 2783171
This is around a 7.7% slowdown - that I hope to fix with a better malloc.
While this doesn't really make the code that much simpler, it doesn't feel
like the right approach in the first place
|
|
* I'm being more strict about the linked list state to hopefully ensure
I'm not leaking any references.
* vfsreq_create was renamed to vfsreq_dispatchcopy as that name feels more
clear. It copies its argument, and dispatches it.
* Requests for user backends are now handled more like requests for kernel
backends - there's an accept() function that accepts a request.
|
|
|
|
|
|
|
|
|
|
|
|
I probably should've tested DUP_WRONLY too, now that I think about it. TODO?
|
|
It was a dumb hack that wasn't even necessary - an error when mounting should
shadow over the mountpoint anyways.
|
|
|
|
|
|
|
|
what the fuck was I thinking when I originally implemented that?
|
|
|
|
|
|
time() will probably end up doing io. That sounded bad at first, but Plan 9
does that too (see /sys/src/libc/9sys/nsec.c), so it's probably fine.
I might need better service management soon. Also, dunno what it should return
before it makes contact with NTP.
I could implement RTC support, but eh. Doesn't feel that necessary.
I'll also need to remember how the hell threading works, so it can talk with
the ntp daemon on another thread.
|
|
|
|
|
|
the vm isn't getting an NMI for any real reason anyways, so I might as well
abuse it
|
|
|
|
|
|
|
|
|
|
|
|
pretty useless, but the list of all the TODOs is getting unwieldy, so I might
as well cross some crap off that list
|
|
I can now actually curl an entire page :^)
|
|
/usr/share/hosts because i don't have /etc/ yet and i don't feel like creating it.
|
|
|
|
had to do a lot of hacky stuff, but it's there.
worked on this on and off for a while now
|
|
|
|
|
|
not sure how that slipped by
|
|
|
|
|
|
|
|
|
|
|
|
not strictly necessary, but this should improve:
1. sleep performance
2. power efficiency when idle
|
|
After some consideration this seems like the most fitting way to handle
timekeeping. Directly, the syscall is only useful for keeping time within a
single process, but it is meant to be used for e.g. NTP clients, which will
provide the real time through the VFS.
|
|
|
|
|
|
|
|
moved keyboard and vtty to /dev/, removed some obsolete stuff
|
