[lkml]   [2005]   [Mar]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    Subject[ANNOUNCE] Robust Mutex Special Interest Group

    Announcing the OSDL Robust Mutex Special Interest Group


    The general mission of the mutexes SIG is to establish a forum centralizing discussion pertaining to mutex-specific planning and
    development in Linux.

    The mutexes SIG is needed to promote forward-looking discussion between developers, users and maintainers.

    The mutexes SIG can reduce redundant development efforts, and could provision a base for exploring successful integration of
    mutex-related technology into the Linux kernel.


    Mutex implementations, like the applications that use them are plentiful. Mutex implementations are found in Linux libraries, in
    Linux patches, as well as the Linux Kernel.

    For each mutex implementation, functionality is specialized. Almost all multi-threaded applications depend on mutexes. College
    textbooks cite examples that work on Linux, but use mutex libraries dating back to older operating systems.

    Amazing applications, some as mobile as autonomous Robots, run Linux, but many of them augment the Linux kernel with mutex
    enhancements that comply with given design criteria.

    Advanced mutex functionality is minimal in the Linux kernel. With the advent of the real-time preemption concept, the mutex
    conundrum does not relent.

    The real-time enhancements exist only as a kernel patch, as do many of the mutex implementations. But the real-time mutex
    implementation is not compatible with any other advanced mutex implementation.


    The mutexes SIG will initially research the integration of two partially overlapped mutex implementations:


    The realtime-preempt mutex in Ingo Molnar's patch implements a generic (portable) priority-inheriting kernel mutex with deadlock
    detection support.

    The Robust Mutex project (aka "Fusyn") also provides a generic (portable) priority-inheriting kernel / userspace mutex with deadlock

    Both projects have specific, but also complementary, and overlapping objectives. Both projects implement several possibly common
    subsystems, but the implementations are functionally conflicting. Binary compatibility concerns emerge.

    It is conceivable that system-designers using Linux for advanced applications may wish to utilize the Robust (User-space) Mutex
    patches at the same time as the real-time kernel enhancements. It is inefficient at best, to have two independent PI mechanisms
    operating in the kernel. If RT and Fusyn are to coexist (they are birds of a feather
    after all), at least the priority inhertance functionality, as well as bounded list operations would need to be reconciled between
    the two implementations.

    Please refer to the OSDL site:

    for more information.

    First conference call is Wed (3/16) at 9AM (pacific)

    Thank You


    Sven-Thorsten Dietrich
    Real-Time Software Architect
    MontaVista Software, Inc.
    1237 East Arques Ave.
    Sunnyvale, CA 94085

    Phone: 408.992.4515
    Fax: 408.328.9204
    Platform To Innovate

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:11    [W:0.025 / U:18.412 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site