Le 07/12/2016 à 02:06, Scott Wood a écrit :
On Tue, 2016-12-06 at 07:34 +0100, Christophe LEROY wrote:
Le 06/12/2016 à 02:18, Scott Wood a écrit :
On Wed, 2016-09-21 at 10:11 +0200, Christophe Leroy wrote:
Today there are two implementations of hugetlbpages which are managed
by exclusive
On Tue, 2016-12-06 at 07:34 +0100, Christophe LEROY wrote:
>
> Le 06/12/2016 à 02:18, Scott Wood a écrit :
> >
> > On Wed, 2016-09-21 at 10:11 +0200, Christophe Leroy wrote:
> > >
> > > Today there are two implementations of hugetlbpages which are managed
> > > by exclusive #ifdefs:
> > > *
Le 06/12/2016 à 02:18, Scott Wood a écrit :
On Wed, 2016-09-21 at 10:11 +0200, Christophe Leroy wrote:
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
On Wed, 2016-09-21 at 10:11 +0200, Christophe Leroy wrote:
> 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
Christophe Leroy writes:
> 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
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