[lkml]   [2005]   [Apr]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectFUSYN and RT

    I just wanted to discuss the problem a little more. From all the
    conversations that I've had it seem that everyone is worried about
    having PI in Fusyn, and PI in the RT mutex.

    It seems like these two locks are going to interact on a very limited
    basis. Fusyn will be the user space mutex, and the RT mutex is only in
    the kernel. You can't lock an RT mutex and hold it, then lock a Fusyn
    mutex (anyone disagree?). That is assuming Fusyn stays in user space.

    The RT mutex will never lower a tasks priority lower than the priority
    given to it by locking a Fusyn lock.

    At least, both mutexes will need to use the same API to raise and lower

    The next question is deadlocks. Because one mutex is only in the kernel,
    and the other is only in user space, it seems that deadlocks will only
    occur when a process holds locks that are all the same type.


    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-04-12 21:59    [W:0.018 / U:2.148 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site