From: | Sean Chittenden <sean(at)chittenden(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kevin Brown <kevin(at)sysexperts(dot)com>, pgsql-performance(at)postgresql(dot)org |
Subject: | Re: First set of OSDL Shared Mem scalability results, some wierdness ... |
Date: | 2004-10-15 20:16:27 |
Message-ID: | 17EBD8C6-1EE7-11D9-A0BB-000A95C705DC@chittenden.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers 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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-10-15 20:34:02 | Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ... |
Previous Message | Josh Berkus | 2004-10-15 20:13:13 | Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ... |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2004-10-15 20:34:02 | Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ... |
Previous Message | Josh Berkus | 2004-10-15 20:13:13 | Re: [Testperf-general] Re: First set of OSDL Shared Memscalability results, some wierdness ... |