Messages in this thread | | | Date | Thu, 9 Jan 2003 16:55:10 -0800 | From | William Lee Irwin III <> | Subject | Re: 2.4.20, .text.lock.swap cpu usage? (ibm x440) |
| |
At some point in the past, I wrote: >> Either pollwait tables (invisible in 2.4 and 2.5), kernel stacks of >> threads (which don't get pae_pgd's and are hence invisible in 2.4 >> and 2.5), or pagecache, with a much higher likelihood of pagecache.
On Thu, Jan 09, 2003 at 06:44:10PM -0600, Brian Tinsley wrote: > The "kernel stacks of threads" may have some bearing on my incarnation > of this problem. We have several heavily threaded Java applications > running at the time the live-locks occur. At our most problematic site, > one application has a bug that can cause hundreds of timer threads (I > mean like 800 or so!) to be "accidentally" created. This site is > scheduled for an upgrade either tonight or tomorrow, so I will leave the > system as it is and see if I can still cause the live-lock to manifest > itself after the upgrade.
There is no extant implementation of paged stacks yet. I'm working on a different problem (mem_map on 64GB on 2.5.x). I probably won't have time to implement it in the near future, I probably won't be doing it vs. 2.4.x, and I won't have to if someone else does it first.
Bill - 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/
| |