From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: Huge page(contiguous bit) slow down
Date: Wed, 19 Sep 2018 17:05:12 +0100 [thread overview]
Message-ID: <20180919160511.GE22723@arm.com> (raw)
In-Reply-To: <20180919153658.udwxks7p4saqvmt2@capper-debian.cambridge.arm.com>
On Wed, Sep 19, 2018 at 04:37:08PM +0100, Steve Capper wrote:
> On Wed, Sep 19, 2018 at 11:29:37AM +0100, Will Deacon wrote:
> > diff --git a/arch/arm64/mm/hugetlbpage.c b/arch/arm64/mm/hugetlbpage.c
> > index 192b3ba07075..edae6774132d 100644
> > --- a/arch/arm64/mm/hugetlbpage.c
> > +++ b/arch/arm64/mm/hugetlbpage.c
> > @@ -324,7 +324,7 @@ int huge_ptep_set_access_flags(struct vm_area_struct *vma,
> > unsigned long addr, pte_t *ptep,
> > pte_t pte, int dirty)
> > {
> > - int ncontig, i, changed = 0;
> > + int ncontig, i;
> > size_t pgsize = 0;
> > unsigned long pfn = pte_pfn(pte), dpfn;
> > pgprot_t hugeprot;
> > @@ -336,9 +336,14 @@ int huge_ptep_set_access_flags(struct vm_area_struct *vma,
> > ncontig = find_num_contig(vma->vm_mm, addr, ptep, &pgsize);
> > dpfn = pgsize >> PAGE_SHIFT;
> >
> > + for (i = 0; i < ncontig; i++)
> > + if (!pte_same(huge_ptep_get(ptep + i), pte))
> > + break;
> > +
>
> This comparison will always fail as our pfns will be different. I have a work
> in progress fix (a separate function to go through the contiguous range
> to preserve the dirty information) that I'll test and post shortly.
Ha, yes of course. I forgot about the most useful part of the pte!
I'll take a look at your patch when you post it.
Will
next prev parent reply other threads:[~2018-09-19 16:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-18 3:02 Huge page(contiguous bit) slow down Zhang, Lei
2018-09-18 11:33 ` Will Deacon
2018-09-18 14:58 ` Catalin Marinas
2018-09-18 15:16 ` Will Deacon
2018-09-18 16:09 ` Catalin Marinas
2018-09-18 16:14 ` Will Deacon
2018-09-18 17:11 ` Catalin Marinas
2018-09-18 20:30 ` Steve Capper
2018-09-19 10:29 ` Will Deacon
2018-09-19 15:37 ` Steve Capper
2018-09-19 16:05 ` Will Deacon [this message]
2018-09-18 20:26 ` Steve Capper
2018-09-18 15:18 ` Punit Agrawal
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180919160511.GE22723@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).