Re: munmap() failure due to sloppy handling of hugepage size

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>, Abhijit Menon-Sen <ams(at)2ndquadrant(dot)com>
Subject: Re: munmap() failure due to sloppy handling of hugepage size
Date: 2016-10-12 22:18:56
Message-ID: 10256.1476310736@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Merlin Moncure <mmoncure(at)gmail(dot)com> writes:
> ISTM all this silliness is pretty much unique to linux anyways.
> Instead of reading the filesystem, what about doing test map and test
> unmap?

And if mmap succeeds and munmap fails, you'll recover how exactly?

If this API were less badly designed, we'd not be having this problem
in the first place ...

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2016-10-12 22:23:35 Re: munmap() failure due to sloppy handling of hugepage size
Previous Message Merlin Moncure 2016-10-12 22:14:20 Re: munmap() failure due to sloppy handling of hugepage size