diff options
| author | Christophe Leroy <[email protected]> | 2016-12-07 07:47:26 +0000 |
|---|---|---|
| committer | Scott Wood <[email protected]> | 2016-12-10 04:48:09 +0000 |
| commit | 03bb2d65900c87a6cc860310b4d598c68fb83393 (patch) | |
| tree | a75dba81f5c0ce82bb941e5db7077bbdc30cde26 /net/unix/af_unix.c | |
| parent | powerpc: port 64 bits pgtable_cache to 32 bits (diff) | |
| download | kernel-03bb2d65900c87a6cc860310b4d598c68fb83393.tar.gz kernel-03bb2d65900c87a6cc860310b4d598c68fb83393.zip | |
powerpc: get hugetlbpage handling more generic
Today there are two implementations of hugetlbpages which are managed
by exclusive #ifdefs:
* FSL_BOOKE: several directory entries points to the same single hugepage
* BOOK3S: one upper level directory entry points to a table of hugepages
In preparation of implementation of hugepage support on the 8xx, we
need a mix of the two above solutions, because the 8xx needs both cases
depending on the size of pages:
* In 4k page size mode, each PGD entry covers a 4M bytes area. It means
that 2 PGD entries will be necessary to cover an 8M hugepage while a
single PGD entry will cover 8x 512k hugepages.
* In 16 page size mode, each PGD entry covers a 64M bytes area. It means
that 8x 8M hugepages will be covered by one PGD entry and 64x 512k
hugepages will be covers by one PGD entry.
This patch:
* removes #ifdefs in favor of if/else based on the range sizes
* merges the two huge_pte_alloc() functions as they are pretty similar
* merges the two hugetlbpage_init() functions as they are pretty similar
Signed-off-by: Christophe Leroy <[email protected]>
Reviewed-by: Aneesh Kumar K.V <[email protected]> (v3)
Signed-off-by: Scott Wood <[email protected]>
Diffstat (limited to 'net/unix/af_unix.c')
0 files changed, 0 insertions, 0 deletions