lkml.org 
[lkml]   [2001]   [Oct]   [23]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: time tells all about kernel VM's
Date
On Tuesday 23 October 2001 19:42, Rik van Riel wrote:
> On Mon, 22 Oct 2001, safemode wrote:
> > First the kernel created about 600MB of buffer in addition to the
> > application specified 128MB of buffer i had it using (e2defrag -p
> > 16384). This brought the system to a crawl.
>
> Now that I think about it, and read the last message you wrote
> in the thread ... do you have some vmstat output during this
> time ?
>
> Do you know if e2defrag somehow locks buffers into RAM ?
>
e2defrag has a setting to allocate buffers. According to the number i gave
it, it should have allocated 128MB .. this is in accordance to what i
observed in ps aux during the runtime. All vmstat data i had was in buffer
and lost when later i ran the graphviz programs and deadlocked the computer.
I was not expecting to reboot. I can always try it again. e2defrag didn't
deadlock the computer, but it did cause that unusual behavior that i observed
just before deadlocking it with graphviz. What kind of vmstat output do you
want, every 10 seconds?
-
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 13:10    [W:0.149 / U:0.492 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site