Date: Tue, 28 Feb 2012 22:06:12 +0100 (CET) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: Artem Belevich <art@freebsd.org> Cc: freebsd-hackers@freebsd.org, Grzegorz Kulewski <grzegorz@kulewski.pl>, Andriy Gapon <avg@freebsd.org> Subject: Re: improving VM - questions Message-ID: <alpine.BSF.2.00.1202282205350.32088@wojtek.tensor.gdynia.pl> In-Reply-To: <CAFqOu6hy9S5PHcff4YnoMow5%2BpNT%2Bs_7PXLq%2B1%2BHuiBrW%2BG3yQ@mail.gmail.com> 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> <4F4CAAC1.9060908@FreeBSD.org> <CAFqOu6hy9S5PHcff4YnoMow5%2BpNT%2Bs_7PXLq%2B1%2BHuiBrW%2BG3yQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
--2456600518-547007317-1330463172=:32088 Content-Type: TEXT/PLAIN; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE >>> right. but still 32 pages is 128kB, but i see 64kB I/Os in systat/vmsta= t >> >> Right, but the comment says to not define MAX_PAGEOUT_CLUSTER to a value= greater >> than 32, but you did that. =C2=A0So all bets could be off unless you exa= mined the >> code and know exactly what should happen in this case. > > I suspect it might be DFLTPHYS that splits disk i/o into 64K blocks on > the driver level. can i increase DFLTPHYS as well as i did with MAXPHYS without problems? --2456600518-547007317-1330463172=:32088--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1202282205350.32088>