[lkml]   [2004]   [Aug]   [12]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: [patch] voluntary-preempt-2.6.8-rc3-O5
    On Thu, 2004-08-12 at 20:04, Lee Revell wrote:

    > So, it seems that if a SCHED_FIFO process opens a PCM device using mmap,
    > then mlockall's the memory, then another process mlockall's memory, the
    > result is an xrun 100% of the time.

    I have found that around 1400 KB is a magic number on my system, this
    triggers the preempt violation/xrun about 50% of the time. 1300 never
    triggers it, 1500 always triggers it.

    Also the amount of memory being mlockall'ed does not affect the length
    of the preemption violation - if we hit it at all, there's a 10ms
    latency, whether we lock 1400KB or 100MB.

    Hopefully O6 will give enough info to track this down.


    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:05    [W:0.019 / U:36.372 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site