lkml.org 
[lkml]   [2008]   [Jul]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    Date
    From
    SubjectRe: [PATCH] stopmachine: add stopmachine_timeout


    Hidetoshi Seto wrote:
    > Heiko Carstens wrote:
    >> Hmm.. probably a stupid question: but what could happen that a real cpu
    >> (not virtual) becomes unresponsive so that it won't schedule a MAX_RT_PRIO-1
    >> prioritized task for 5 seconds?
    >
    > The original problem (once I heard and easily reproduced) was there was an
    > another MAX_RT_PRIO-1 task and the task was spinning in itself by a bug.
    > (Now this would not be a problem since RLIMIT_RTTIME will work for it, but
    > I cannot deny that there are some situations which cannot set the limit.)
    Yep. As I described in the prev email in my case it's a legitimate thing. Some
    of the CPU cores are running wireless basestation schedulers and the deadlines
    are way too tight for them to sleep (it's "cpu as a dedicated engine" kind of
    thing, they are properly isolated and stuff).

    In this case actually RT limit is the first thing that I disable :).
    I'd rather have stop_machine fail and tell the user that something is wrong.
    In which case they can simply stop the basestation app that is running when
    convinient. ie It give control back to the user rather than wedging the box or
    killing the app.

    Max


    \
     
     \ /
      Last update: 2008-07-15 04:43    [W:9.219 / U:0.164 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site