From: Naoya Horiguchi <n-horiguchi@ah.jp.nec.com>
To: dave@sr71.net
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
"Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>
Subject: [PATCH -mm] mincore: apply page table walker on do_mincore() (Re: [PATCH 00/10] mm: pagewalk: huge page cleanups and VMA passing)
Date: Tue, 3 Jun 2014 02:18:16 -0400 [thread overview]
Message-ID: <538d68b1.e8648c0a.a45f.23f8SMTPIN_ADDED_BROKEN@mx.google.com> (raw)
In-Reply-To: <538CF25E.8070905@sr71.net>
On Mon, Jun 02, 2014 at 02:53:34PM -0700, Dave Hansen wrote:
> On 06/02/2014 02:52 PM, Naoya Horiguchi wrote:
> > What version is this patchset based on?
> > Recently I comprehensively rewrote page table walker (from the same motivation
> > as yours) and the patchset is now in linux-mm. I guess most of your patchset
> > (I've not read them yet) conflict with this patchset.
> > So could you take a look on it?
>
> It's on top of a version of Linus's from the last week. I'll take a
> look at how it sits on top of -mm.
I've looked over your series, but unfortunately most of works (patch 1, 2, 3,
5, 6, 7) were already done or we don't have to do it in current linux-mm code.
Problems you try to handle in these patches come from current code's poor
design of page table walker, worst thing is that we do vma-loop inside pgd loop.
I know you tried harder to make things better, but I don't think it make sense
to maintain current bad base code for long.
As for patch 4, yes, we can apply page table walker do_mincore() and I have
a patch applicable onto linux-mm code (attached). And for other potential
page walk users, I'm investigating whether we can really apply page table
walker (some caller doesn't hold mmap_sem, so can't simply apply it.)
And for patch 8, 9, and 10, I don't think it's good idea to add a new callback
which can handle both pmd and pte (because they are essentially differnt thing).
But the underneath idea of doing pmd_trans_huge_lock() in the common code in
walk_single_entry_locked() looks nice to me. So it would be great if we can do
the same thing in walk_pmd_range() (of linux-mm) to reduce code in callbacks.
Thanks,
Naoya Horiguchi
---
next prev parent reply other threads:[~2014-06-03 6:18 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-02 21:36 [PATCH 00/10] mm: pagewalk: huge page cleanups and VMA passing Dave Hansen
2014-06-02 21:36 ` [PATCH 01/10] mm: pagewalk: consolidate vma->vm_start checks Dave Hansen
2014-06-02 21:36 ` [PATCH 02/10] mm: pagewalk: always skip hugetlbfs except when explicitly handled Dave Hansen
2014-06-02 21:36 ` [PATCH 03/10] mm: pagewalk: have generic code keep track of VMA Dave Hansen
2014-06-02 21:36 ` [PATCH 04/10] mm: pagewalk: add page walker for mincore() Dave Hansen
2014-06-02 21:36 ` [PATCH 05/10] mm: mincore: clean up hugetlbfs handling (part 1) Dave Hansen
2014-06-02 21:36 ` [PATCH 06/10] mm: mincore: clean up hugetlbfs handler (part 2) Dave Hansen
2014-06-02 21:36 ` [PATCH 07/10] mm: pagewalk: kill check for hugetlbfs inside /proc pagemap code Dave Hansen
2014-06-02 21:36 ` [PATCH 08/10] mm: pagewalk: add locked pte walker Dave Hansen
2014-06-02 21:36 ` [PATCH 09/10] mm: pagewalk: use new locked walker for /proc/pid/smaps Dave Hansen
2014-06-02 21:36 ` [PATCH 10/10] mm: pagewalk: use locked walker for /proc/pid/numa_maps Dave Hansen
2014-06-02 21:52 ` [PATCH 00/10] mm: pagewalk: huge page cleanups and VMA passing Naoya Horiguchi
[not found] ` <1401745925-l651h3s9@n-horiguchi@ah.jp.nec.com>
2014-06-02 21:53 ` Dave Hansen
2014-06-03 6:18 ` Naoya Horiguchi [this message]
[not found] ` <1401776292-dn0fof8e@n-horiguchi@ah.jp.nec.com>
2014-06-03 15:55 ` [PATCH -mm] mincore: apply page table walker on do_mincore() (Re: [PATCH 00/10] mm: pagewalk: huge page cleanups and VMA passing) Dave Hansen
2014-06-03 20:01 ` Naoya Horiguchi
2014-06-03 20:08 ` Naoya Horiguchi
[not found] ` <1401825676-8py0r32h@n-horiguchi@ah.jp.nec.com>
2014-06-03 20:33 ` Dave Hansen
2014-06-03 15:59 ` Dave Hansen
2014-06-03 16:22 ` Naoya Horiguchi
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=538d68b1.e8648c0a.a45f.23f8SMTPIN_ADDED_BROKEN@mx.google.com \
--to=n-horiguchi@ah.jp.nec.com \
--cc=dave@sr71.net \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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