From: | yamt(at)mwd(dot)biglobe(dot)ne(dot)jp (YAMAMOTO Takashi) |
---|---|
To: | tgl(at)sss(dot)pgh(dot)pa(dot)us |
Cc: | robertmhaas(at)gmail(dot)com, andres(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org, josh(at)agliodbs(dot)com |
Subject: | Re: huge tlb support |
Date: | 2012-07-09 05:32:15 |
Message-ID: | 20120709053215.C1E8614A1BD@mail.netbsd.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Fri, Jun 29, 2012 at 3:52 PM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>>> In a *very* quick patch I tested using huge pages/MAP_HUGETLB for the mmap'ed
>>> memory.
>
>> So, considering that there is required setup, it seems that the
>> obvious thing to do here is add a GUC: huge_tlb_pages (boolean).
>
>> The other alternative is to try with MAP_HUGETLB and, if it fails, try
>> again without MAP_HUGETLB.
>
> +1 for not making people configure this manually.
>
> Also, I was under the impression that recent Linux kernels use hugepages
> automatically if they can, so I wonder exactly what Andres was testing
> on ...
if you mean the "trasparent hugepage" feature, iirc it doesn't affect
MAP_SHARED mappings like this.
YAMAMOTO Takashi
>
> regards, tom lane
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2012-07-09 06:11:00 | Re: huge tlb support |
Previous Message | Kohei KaiGai | 2012-07-09 04:38:58 | Re: pgsql_fdw in contrib |