Date: Tue, 28 Feb 2012 12:21:53 +0200 From: Andriy Gapon <avg@FreeBSD.org> To: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> Cc: freebsd-hackers@FreeBSD.org, Grzegorz Kulewski <grzegorz@kulewski.pl> Subject: Re: improving VM - questions Message-ID: <4F4CAAC1.9060908@FreeBSD.org> In-Reply-To: <alpine.BSF.2.00.1202281043170.1739@wojtek.tensor.gdynia.pl> References: <alpine.BSF.2.00.1202251630560.1436@wojtek.tensor.gdynia.pl> <4F4C0726.6010804@FreeBSD.org> <alpine.BSF.2.00.1202281043170.1739@wojtek.tensor.gdynia.pl>
next in thread | previous in thread | raw e-mail | index | archive | help
on 28/02/2012 11:43 Wojciech Puchar said the following: >>> +++ swap_pager.c 2012-02-25 13:19:51.000000000 +0100 >>> @@ -119,7 +119,7 @@ >>> * The 32-page limit is due to the radix code (kern/subr_blist.c). >>> */ >>> #ifndef MAX_PAGEOUT_CLUSTER >>> -#define MAX_PAGEOUT_CLUSTER 16 >>> +#define MAX_PAGEOUT_CLUSTER 256 >>> #endif >> [snip] >>> but swap_pager.c patch seems not to work. i observe 64kB pageouts, no more. >>> >>> what is wrong in it? >> >> Could there be a problem because of what the MAX_PAGEOUT_CLUSTER comment says? > > right. but still 32 pages is 128kB, but i see 64kB I/Os in systat/vmstat Right, but the comment says to not define MAX_PAGEOUT_CLUSTER to a value greater than 32, but you did that. So all bets could be off unless you examined the code and know exactly what should happen in this case. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4F4CAAC1.9060908>