On Thu, Oct 03, 2013 at 04:11:09PM -0700, Andrew Morton wrote:
> On Fri, 27 Sep 2013 16:16:26 +0300 "Kirill A. Shutemov"
> wrote:
>
> > The basic idea is the same as with PTE level: the lock is embedded into
> > struct page of table's page.
> >
> > We can't use mm->pmd_huge_pte to store pgtable
Andrew Morton wrote:
> On Fri, 27 Sep 2013 16:16:26 +0300 "Kirill A. Shutemov"
> wrote:
>
> > The basic idea is the same as with PTE level: the lock is embedded into
> > struct page of table's page.
> >
> > We can't use mm->pmd_huge_pte to store pgtables for THP, since we don't
> > take mm->pag
On Fri, 27 Sep 2013 16:16:26 +0300 "Kirill A. Shutemov"
wrote:
> The basic idea is the same as with PTE level: the lock is embedded into
> struct page of table's page.
>
> We can't use mm->pmd_huge_pte to store pgtables for THP, since we don't
> take mm->page_table_lock anymore. Let's reuse pag
The basic idea is the same as with PTE level: the lock is embedded into
struct page of table's page.
We can't use mm->pmd_huge_pte to store pgtables for THP, since we don't
take mm->page_table_lock anymore. Let's reuse page->lru of table's page
for that.
pgtable_pmd_page_ctor() returns true, if i
4 matches
Mail list logo