From: Bruce Momjian <pgman@candle.pha.pa.us>
To: Curt Sampson <cjs@cynic.net>
Cc: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
Cc: scott.marlowe <scott.marlowe@ihs.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Greg Copeland <greg@CopelandConsulting.Net>
Cc: PostgresSQL Hackers Mailing List <pgsql-hackers@postgresql.org>
Subject: Re: Changing the default configuration (was Re:
Date: Thu, 13 Feb 2003 13:49:06 -0500 (EST)
Message-ID: <200302131849.h1DIn6r01827@candle.pha.pa.us> (raw)
In-Reply-To: <Pine.NEB.4.51.0302131325430.1487@angelic.cynic.net>
I was speaking of the 4.4 BSD. FreeBSD has the merged VM, and I think
NetBSD only recently did that. BSD/OS does do the locking by default
and it maps into the kernel address space. I believe FreeBSD has a
sysctl to control locking of SysV memory.
One advantage of having it all at the same VM address is that they can
use the same page tables for virtual address lookups.
---------------------------------------------------------------------------
Curt Sampson wrote:
> On Wed, 12 Feb 2003, Bruce Momjian wrote:
>
> > Christopher Kings-Lynne wrote:
> >
> > > You cannot change SHMMAX on the fly on FreeBSD.
> >
> > And part of the reason is because some/most BSD's map the page tables
> > into physical RAM (kernel space) rather than use some shared page table
> > mechanism. This is good because it prevents the shared memory from
> > being swapped out (performance disaster).
>
> Not at all! In all the BSDs, as far as I'm aware, SysV shared memory is
> just normal mmap'd memory.
>
> FreeBSD offers a sysctl that lets you mlock() that memory, and that is
> helpful only because postgres insists on taking data blocks that are
> already in memory, fully sharable amongst all back ends and ready to be
> used, and making a copy of that data to be shared amongst all back ends.
>
> > It doesn't actually allocate RAM unless someone needs it, but it does
> > lock the shared memory into a specific fixed location for all processes.
>
> I don't believe that the shared memory is not locked to a specific VM
> address for every process. There's certainly no reason it needs to be.
>
> cjs
> --
> Curt Sampson <cjs@cynic.net> +81 90 7737 2974 http://www.netbsd.org
> Don't you know, in this new Dark Age, we're all light. --XTC
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: pgman@candle.pha.pa.us, cjs@cynic.net, chriskl@familyhealth.com.au, scott.marlowe@ihs.com, tgl@sss.pgh.pa.us, greg@CopelandConsulting.Net, pgsql-hackers@postgresql.org
Subject: Re: Changing the default configuration (was Re:
In-Reply-To: <200302131849.h1DIn6r01827@candle.pha.pa.us>
References: <Pine.NEB.4.51.0302131325430.1487@angelic.cynic.net> <200302131849.h1DIn6r01827@candle.pha.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox