| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Radosław Smogura <rsmogura(at)softperience(dot)eu> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, Greg Stark <gsstark(at)mit(dot)edu>, Robert Haas <robertmhaas(at)gmail(dot)com>, Greg Smith <greg(at)2ndquadrant(dot)com>, Joshua Berkus <josh(at)agliodbs(dot)com>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: MMAP Buffers |
| Date: | 2011-04-16 23:35:45 |
| Message-ID: | 12299.1302996945@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
=?utf-8?q?Rados=C5=82aw_Smogura?= <rsmogura(at)softperience(dot)eu> writes:
> No, no, no :) I wanted to do this, but from above reason I skipped it. I swap
> VM pages, I do remap, in place where the shared buffer was I put mmaped page,
> and in place where mmaped page was I put shared page (in certain cases, which
> should be optimized by e. g. read for update, for initial read of page in
> process I directly points to shared buffer), it can be imagined as I affects
> TLB. This what I call "VM swap" is remapping, so I don't change pointers, I
> change only where this pointers points in physical memory, preserving same
> pointer in Virtual Memory.
... Huh? Are you saying that you ask the kernel to map each individual
shared buffer separately? I can't believe that's going to scale to
realistic applications.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2011-04-16 23:40:57 | Re: ALTER TABLE INHERIT vs collations |
| Previous Message | Greg Smith | 2011-04-16 23:19:21 | Re: MMAP Buffers |