On Tue, 2006-03-14 at 22:22 +0100, Ingo Molnar wrote:
> * Lee Revell <[email protected]> wrote:
>
> > I've been testign for weeks with 2.6.16-rc1 + the latency trace patch
> > and the longest latencies measured were 10-15ms due to the well known
> > rt_run_flush issue. Today I got one twice as long, when a Firefox
> > process with a bunch of acroreads in tabs, from a new code path.
> >
> > It seems to trigger when a process with a large amount of memory
> > swapped out exits.
>
> btw., one good way to get such things fixed is to code up a testcase: a
> .c file that just has to be run to reproduce the latency. It might be
> less trivial to code that up in some cases (like this one - e.g. you
> might have to first get a large chunk of memory swapped out which isnt
> easy), but i think it's still worth the effort, as that way you can
> gently pressure us lazy upstream maintainers to act quicker, and we can
> also easily verify whether the fix does the trick :-)
Sure, I'll try. But I've been pounding on this kernel for weeks and
only hit this once. And I'm pretty sure I've killed processes with lots
of swapped memory. The only new variable was acroread - open 5 PDFs in
Firefox tabs, leave it alone for a few days until the kernel swaps it
all out, then kill it...
Lee
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
