[lkml]   [2004]   [Aug]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [patch] preempt-timing-on-2.6.8-rc2-O2
On Mon, Aug 02, 2004 at 12:35:16PM +0200, Ingo Molnar wrote:
> i've re-uploaded the -O2 patch with this fixed:
> but i'm still seeing some latencies:
> (kjournald/189): 997us non-preemptible critical section violated 100 us
> preempt threshold starting at journal_commit_transaction+0x642/0x2b10
> and ending at journal_commit_transaction+0x24ce/0x2b10
> [<c0105d7e>] dump_stack+0x1e/0x30
> [<c011ad0f>] dec_preempt_count+0x3f/0x50
> [<c01dfd3e>] journal_commit_transaction+0x24ce/0x2b10
> [<c01e3bf4>] kjournald+0x1a4/0x710
> [<c0102765>] kernel_thread_helper+0x5/0x10
> these should not happen with vp=3 and max_sectors=16. Could you
> double-check the patch above, does it have any other timing thinko?

The false negative I mentioned was the last unresolved issue I knew of.
A brief examination of your updated patch didn't help me to spot any
false positives that haven't been reported yet.

It may help to find the line numbers corresponding to the above
(actually, the way the macros are hooked, the files, functions, line
numbers could be reported directly by the implementation) so we can get
a better idea if this is a false positive or a real 997us long non-
preemptible critical section.

-- wli
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:04    [W:0.381 / U:0.736 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site