Alexander van der Grinten

icon indicating an email [email protected]

icon company BlueRock Security Inc. icon location Germany icon location Low-level enthusiast and OS engineer with focus on microkernels. PhD in CS (solvers for NP-hard problems, network algorithms, parallel algorithms).

Results 119 comments of Alexander van der Grinten

Add a git port

I'm not a fan of doing that; we should just implement POSIX timers.

docker: Add 2 dependencies for swi-prolog

I'm not sure if we shouldn't build these ourselves, especially if we already build them for Managarm, too.

Track reproducibility of packages

Here are some more thoughts on this: Definitions: * Call a package *n-times reproduced* if the last (n+1) builds produced the same file hash. Note that is important that we...

Track reproducibility of packages

Actually, the following might be simpler: For each package, we build a table with one row per build and (build number, version, hash) as columns. Then, if there are two...

Exceptions in coroutines?

There's no technical reason why this cannot work, we just didn't implement it. If you have a (partial) implementation, we'd gladly merge it. Adding support to the basic coroutine types...

Use on platforms that have no mutexes

Mutexes can also make sense in a cooperate scheduling world. For example, Boost's `Fiber` library also has mutexes (which will simply invoke the cooperative scheduler if there is contention). Does...

More (granular) run selection options based on status

:+1:

Allow threads to control when kernel work is executed in their context

For example, this may be useful to block kernel work while userspace is currently processing events from a `HelQueue`. This may improve performance by reducing the number of `workOnExecutor()` calls.

thor: Investigate use of preemption locks

This is mainly useful for CPU local data that we do not access from IRQs. We do not want to hold spinlocks while disabling preemption as that might introduce unexpected...