| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
doesn't really prevent anything, and makes it harder to test edge cases
|
|
|
|
|
|
The old name could have suggested that it held a response to a request
received by fs_wait. The new name is unfortunately very similar to
the `struct vfs_request` already used internally in the kernel, but
it's better at conveying that it contains a filesystem request yet to
be handled.
vfs_request - virtual filesystem request (a bad name in hindsight)
ufs_request - user filesystem request
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
* changed vfs_root_register's name because the _mount didn't add anything
* removed the old pointless vfs_backend_tryaccept calls from drivers
* because of that, i could remove the vfs_backend globals
* replaced the horrible BACKEND_KERN macro
* all vfs_backends are now stored on the heap
|
|
|
|
|
|
|
|
I was reading from the buffer as if the WRAP flag was enabled, but it
actually isn't supported with a 64K buffer.
Besides, if it worked correctly, then the code for updating the ring
position would land in the wrong place, because it didn't take WARP
into account.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Those had a lot of repeating code, but I'm not sure if this is the
right change. Well, apart from making pipe_joinqueue more consistent.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
~3x speedup in tests
|
|
|
