Re: First set of OSDL Shared Mem scalability results, some wierdness ... - Mailing list pgsql-performance

From Sean Chittenden
Subject Re: First set of OSDL Shared Mem scalability results, some wierdness ...
Date
Msg-id 17EBD8C6-1EE7-11D9-A0BB-000A95C705DC@chittenden.org
Whole thread Raw
In response to Re: First set of OSDL Shared Mem scalability results, some wierdness ...  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-performance
> this.  The SUS text is a bit weaselly ("the application must ensure
> correct synchronization") but the HPUX mmap man page, among others,
> lays it on the line:
>
>      It is also unspecified whether write references to a memory region
>      mapped with MAP_SHARED are visible to processes reading the file
> and
>      whether writes to a file are visible to processes that have
> mapped the
>      modified portion of that file, except for the effect of msync().
>
> It might work on particular OSes but I think depending on such behavior
> would be folly...

Agreed.  Only OSes with a coherent file system buffer cache should ever
use mmap(2).  In order for this to work on HPUX, msync(2) would need to
be used.  -sc

--
Sean Chittenden


pgsql-performance by date:

Previous
From: Josh Berkus
Date:
Subject: Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...
Next
From: Tom Lane
Date:
Subject: Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ...