Re: [RFC/PATCH] FUSYN Realtime & robust mutexes for Linux, v2.3.1

[Ingo Molnar]

* Perez-Gonzalez, Inaky <inaky.perez-gonzalez@xxxxxxxxx> wrote:

> Fusyn aims to provide primitives to solve a bunch of gaps in POSIX
> compliance related to mutexes, conditional variables and semaphores,
> POSIX Advanced real-time support as well as adding mutex robustness
> (to dying owners) and deep deadlock checking.

the sched.c bits look clean enough.

i like the generic concept - keeping the userspace fast-path for
lock/unlock, like for futexes, and registering/unregistering a lock via
the kernel.

but, couldnt there be more sharing between futex.c and fusyn.c? In
particular on the API side, why arent all these ops done as an extension
to sys_futex()? That would keep the glibc part much simpler (and more
compatible) as well. You'd still get all the glory of implementing true
priority inheritance and advanced RT-locking for Linux :-)

or are the two interfaces way too different?

	Ingo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/