lkml.org 
[lkml]   [2001]   [Jun]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: Break 2.4 VM in five easy steps
Date
On Thursday 07 June 2001 13:00, Marcelo Tosatti wrote:
> On Thu, 7 Jun 2001, Shane Nay wrote:
> > (Oh, BTW, I really appreciate the work that people have done on the VM,
> > but folks that are just talking..., well, think clearly before you impact
> > other people that are writing code.)
>
> If all the people talking were reporting results we would be really happy.
>
> Seriously, we really lack VM reports.

Okay, I've had some problems with the VM on my machine, what is the most
usefull way to compile reports for you? I have modified the kernel for a few
different ports fixing bugs, and device drivers, etc., but the VM is all
greek to me, I can just see that caching is hyper aggressive and doesn't look
like it's going back to the pool..., which results in sluggish performance.
Now I know from the work that I've done that anecdotal information is almost
never even remotely usefull. Therefore is there any body of information that
I can read up on to create a usefull set of data points for you or other VM
hackers to look at? (Or maybe some report in the past that you thought was
especially usefull?)

Thank You,
Shane Nay.
(I have in the past had many problems with the VM on embedded machines as
well, but I'm not actively working on any right this second..., though my
Psion is sitting next to me begging for me to run some VM tests on it :)
-
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 12:55    [W:0.078 / U:7.288 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site