xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: 2.4.20pre5aa2

from [Samuel Flory] [Permanent Link][Original]
To: Andrea Arcangeli <andrea@xxxxxxx>
Subject: Re: 2.4.20pre5aa2
From: Samuel Flory <sflory@xxxxxxxxxxxx>
Date: Fri, 13 Sep 2002 14:09:54 -0700
Cc: Stephen Lord <lord@xxxxxxx>, Austin Gonyou <austin@xxxxxxxxxxxxxxx>, Christian Guggenberger <christian.guggenberger@xxxxxxxxxxxxxxxxxxxxxxxx>, Linux Kernel <linux-kernel@xxxxxxxxxxxxxxx>, linux-xfs@xxxxxxxxxxx
References: <20020911201602.A13655@pc9391.uni-regensburg.de> <1031768655.24629.23.camel@UberGeek.coremetrics.com> <20020911184111.GY17868@dualathlon.random> <3D81235B.6080809@rackable.com> <20020913002316.GG11605@dualathlon.random> <1031878070.1236.29.camel@snafu> <20020913005440.GJ11605@dualathlon.random> <3D8149F6.9060702@rackable.com> <20020913125345.GO11605@dualathlon.random>
Sender: linux-xfs-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.1) Gecko/20020826 
Andrea Arcangeli wrote:



you can try to compile with CONFIG_3G and to set __VMALLOC_RESERVE to
(512 << 20) and see if it helps. If it only happens a bit later then
it's most probably an address space leak, should be easy to track down
some debugging instrumentation.




It seems to be working for me now. I'm getting about 200 on dbench 4, and 90 on dbench 64. (Note you need to increase your log size to get these kinda of numbers.) Now I get to see how fast I can read files via nfs.


[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: TAKE - change symlink perms to 777, Nathan Scott
Next by Date:  Re: 2.4.20pre5aa2, Andrea Arcangeli
Previous by Thread:  Re: 2.4.20pre5aa2, Andrea Arcangeli
Next by Thread:  Re: 2.4.20pre5aa2, Andrea Arcangeli
Indexes:  [Date] [Thread] [Top] [All Lists]