Date: Sat, 9 Jun 2012 22:45:56 +0200 (CEST) From: Wojciech Puchar <wojtek@wojtek.tensor.gdynia.pl> To: Konstantin Belousov <kostikbel@gmail.com> Cc: Ian Lepore <freebsd@damnhippie.dyndns.org>, freebsd-hackers@freebsd.org Subject: Re: wired memory - again! Message-ID: <alpine.BSF.2.00.1206092244550.9248@wojtek.tensor.gdynia.pl> In-Reply-To: <20120609165217.GO85127@deviant.kiev.zoral.com.ua> References: <alpine.BSF.2.00.1206090920030.84632@wojtek.tensor.gdynia.pl> <1339259223.36051.328.camel@revolution.hippie.lan> <20120609165217.GO85127@deviant.kiev.zoral.com.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
> > First, all memory allocated by UMA and consequently malloc(9) is > wired. In other words, almost all memory used by kernel is accounted > as wired. > yes i understand this. still i found no way how to find out what allocated that much. > Second, the buffer cache wires the pages which are inserted into VMIO > buffers. So your observation is basically right, cached buffers means what are exactly "VMIO" buffers. i understand that page must be wired WHEN doing I/O. But i have too much wired memory even when doing no I/O at all. > that corresponding memory is removed from queues and put into wired > state. When buffers are dissolved, pages are unwired and deactivated. > > This behaviour is in fact required by VFS, since you do expect to access > buffer data when you get the buffer. >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1206092244550.9248>