pgsql: Add palloc_aligned() to allow aligned memory allocations - Mailing list pgsql-committers

From David Rowley
Subject pgsql: Add palloc_aligned() to allow aligned memory allocations
Date
Msg-id E1p89Vd-004nQg-4y@gemulon.postgresql.org
Whole thread Raw
List pgsql-committers
Add palloc_aligned() to allow aligned memory allocations

This introduces palloc_aligned() and MemoryContextAllocAligned() which
allow callers to obtain memory which is allocated to the given size and
also aligned to the specified alignment boundary.  The alignment
boundaries may be any power-of-2 value.  Currently, the alignment is
capped at 2^26, however, we don't expect values anything like that large.
The primary expected use case is to align allocations to perhaps CPU
cache line size or to maybe I/O page size.  Certain use cases can benefit
from having aligned memory by either having better performance or more
predictable performance.

The alignment is achieved by requesting 'alignto' additional bytes from
the underlying allocator function and then aligning the address that is
returned to the requested alignment.  This obviously does waste some
memory, so alignments should be kept as small as what is required.

It's also important to note that these alignment bytes eat into the
maximum allocation size.  So something like:

palloc_aligned(MaxAllocSize, 64, 0);

will not work as we cannot request MaxAllocSize + 64 bytes.

Additionally, because we're just requesting the requested size plus the
alignment requirements from the given MemoryContext, if that context is
the Slab allocator, then since slab can only provide chunks of the size
that's specified when the slab context is created, then this is not going
to work.  Slab will generate an error to indicate that the requested size
is not supported.

The alignment that is requested in palloc_aligned() is stored along with
the allocated memory.  This allows the alignment to remain intact through
repalloc() calls.

Author: Andres Freund, David Rowley
Reviewed-by: Maxim Orlov, Andres Freund, John Naylor
Discussion: https://postgr.es/m/CAApHDvpxLPUMV1mhxs6g7GNwCP6Cs6hfnYQL5ffJQTuFAuxt8A%40mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/439f61757f054109f9ee5415530a2744f7e5cb7a

Modified Files
--------------
src/backend/utils/cache/catcache.c       |   5 +-
src/backend/utils/mmgr/Makefile          |   1 +
src/backend/utils/mmgr/alignedalloc.c    | 132 ++++++++++++++++++++++++++
src/backend/utils/mmgr/mcxt.c            | 155 +++++++++++++++++++++++++++++--
src/backend/utils/mmgr/meson.build       |   1 +
src/include/utils/memutils_internal.h    |  22 ++++-
src/include/utils/memutils_memorychunk.h |   2 +-
src/include/utils/palloc.h               |   3 +
8 files changed, 308 insertions(+), 13 deletions(-)


pgsql-committers by date:

Previous
From: Tom Lane
Date:
Subject: pgsql: Fix contrib/seg to be more wary of long input numbers.
Next
From: Michael Paquier
Date:
Subject: pgsql: Fix operator typo in tablecmds.c