On Mon, Dec 03, 2001 at 02:55:37AM +0100, Emiel Kollof wrote:
> On Monday 03 December 2001 02:28, David Xu wrote:
> > This is strange, the problem would happen in heavy forked system which
> > have lots of pages
> > are shared between lots of process and most are commited to these
> > processes, this is a known
> > FreeBSD VM problem, the pv_entry are static allocated using vm_zone
> > with max limit set.
> > strange thing is it happens in booting time.
> Yup. This is not a heavily loaded system. I'm not doing an excessive amount
> of shared memory stuff as well, and I am not using sysctl tweaks that effect
> shared mem. The thing is completely default (well, almost, I bumped up
> NMBCLUSTERS and maxusers, and I trimmed the kernel config to excluse stuff my
> laptop simply doesn't have or will never have, like some NIC's and SCSI
> adapters). The machine is a desktop machine that runs KDE 2.2.2 (the testing
> tarballs, see freebsd.kde.org for more info) and actually nothing more.
> So that's actually why I posted it. It struck me as strange as well that this
> should appear, because I've never seen it before. Also tweaking other vm bits
> seems not good, since the VM really does a good job in balancing itself
> already. I shouldn't mess in something that already works.
There are other sources for shared memory than fork.
Several processes mmap'ing the same file might produce it.
One example for this scenario is that you have an ftp server and lot
of fetches to the same big file.
B.Walter COSMO-Project http://www.cosmo-project.de
[EMAIL PROTECTED] Usergroup [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message