lkml.org 
[lkml]   [2004]   [Aug]   [14]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: [patch] voluntary-preempt-2.6.8-rc4-O7
    From
    Date
    On Fri, 2004-08-13 at 06:48, Ingo Molnar wrote:
    > ok, it seems the lock-break of the outer loop was not enough - the up to
    > 1024 iterations in the inner loop can generate quite high latencies too.
    >

    In some of the traces, like this one:

    http://krustophenia.net/testresults.php?dataset=2.6.8-rc4-bk3-O7#/var/www/2.6.8-rc4-bk3-O7/mount_reiserfs_latency_trace.txt

    there are calls to voluntary_resched. How is this possible? Does it
    mean that we called voluntary_resched while holding a spinlock, where we
    needed to call voluntary_preempt_lock(&foo_lock), and thus failed to
    reschedule?

    Lee

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

    \
     
     \ /
      Last update: 2005-03-22 14:05    [W:0.027 / U:90.632 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site