Re: [PATCH] Use MAP_HUGETLB where supported (v3) - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [PATCH] Use MAP_HUGETLB where supported (v3)
Date
Msg-id 20131121210938.GE6041@eldon.alvh.no-ip.org
Whole thread Raw
In response to Re: [PATCH] Use MAP_HUGETLB where supported (v3)  (Abhijit Menon-Sen <ams@2ndQuadrant.com>)
Responses Re: [PATCH] Use MAP_HUGETLB where supported (v3)  (Andres Freund <andres@2ndquadrant.com>)
Re: [PATCH] Use MAP_HUGETLB where supported (v3)  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Abhijit Menon-Sen wrote:
> At 2013-11-15 15:17:32 +0200, hlinnakangas@vmware.com wrote:

> > But I'm not wedded to the idea if someone objects; a log message might
> > also be reasonable: "LOG: huge TLB pages are not supported on this
> > platform, but huge_tlb_pages was 'on'"
> 
> Put that way, I have to wonder if the right thing to do is just to have
> a "try_huge_pages=on|off" setting, and log a warning if the attempt did
> not succeed. It would be easier to document, and I don't think there's
> much point in making it an error if the allocation fails.

What about
huge_tlb_pages={off,try}

Or maybe
huge_tlb_pages={off,try,require}

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1
Next
From: Heikki Linnakangas
Date:
Subject: Re: Data corruption issues using streaming replication on 9.0.14/9.2.5/9.3.1