Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 16 Aug 2004 18:10:18 -0700
From:      "David O'Brien" <obrien@freebsd.org>
To:        Alfred Perlstein <alfred@freebsd.org>
Cc:        cvs-all@freebsd.org
Subject:   Re: cvs commit: src/sys/i386/include vmparam.h
Message-ID:  <20040817011018.GA67171@dragon.nuxi.com>
In-Reply-To: <20040816232834.GF57908@elvis.mu.org>
References:  <200408160835.i7G8ZM6d068546@repoman.freebsd.org> <20040816232834.GF57908@elvis.mu.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Aug 16, 2004 at 04:28:34PM -0700, Alfred Perlstein wrote:
> * David E. O'Brien <obrien@FreeBSD.org> [040816 01:35] wrote:
> > obrien      2004-08-16 08:35:22 UTC
> > 
> >   FreeBSD src repository
> > 
> >   Modified files:
> >     sys/i386/include     vmparam.h 
> >   Log:
> >   Increase the scaling of VM_KMEM_SIZE_MAX.
> 
> Is there any chance we can scale up the max sockets/maxfiles a bit?
> 
> I've found that for simple benchmarks, doubling or quadrupling
> didn't see to cause any instability would make us look better out
> of the box.

The increase of VM_KMEM_SIZE_MAX is prevent (help delay?) panics on 4GB
i386 systems.  Do you have benchmark data suggesting what would be better
values for max sockets/maxfiles?
 
-- 
-- David  (obrien@FreeBSD.org)



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040817011018.GA67171>