linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Kirill A. Shutemov" <kirill@shutemov.name>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Sasha Levin <sasha.levin@oracle.com>
Subject: Re: [PATCH] compaction: fix isolate_migratepages_block() for THP=n
Date: Wed, 29 Apr 2015 01:44:42 +0300	[thread overview]
Message-ID: <20150428224442.GA6188@node.dhcp.inet.fi> (raw)
In-Reply-To: <20150428153724.cbe99bef1e7c2f073755539a@linux-foundation.org>

On Tue, Apr 28, 2015 at 03:37:24PM -0700, Andrew Morton wrote:
> On Wed, 29 Apr 2015 01:28:28 +0300 "Kirill A. Shutemov" <kirill@shutemov.name> wrote:
> 
> > On Tue, Apr 28, 2015 at 03:14:20PM -0700, Andrew Morton wrote:
> > > On Mon, 27 Apr 2015 14:26:46 +0300 "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com> wrote:
> > > 
> > > > PageTrans* helpers are always-false if THP is disabled compile-time.
> > > > It means the fucntion will fail to detect hugetlb pages in this case.
> > > > 
> > > > Let's use PageCompound() instead. With small tweak to how we calculate
> > > > next low_pfn it will make function ready to see tail pages.
> > > 
> > > <scratches head>
> > > 
> > > So this patch has no runtime effects at present?  It is preparation for
> > > something else?
> > 
> > I wrote this to fix bug I originally attributed to refcounting patchset,
> > but Sasha triggered the same bug on -next without the patchset applied:
> >
> > http://lkml.kernel.org/g/553EB993.7030401@oracle.com
> 
> Well why the heck didn't the changelog tell us this?!?!?

Sasha reported bug in -next after I sent the patch.

> 
> > Now I think it's related to changing of PageLRU() behaviour on tail page
> > by my page flags patchset.
> 
> So this patch is a bugfix against one of
> 
> page-flags-trivial-cleanup-for-pagetrans-helpers.patch
> page-flags-introduce-page-flags-policies-wrt-compound-pages.patch
> page-flags-define-pg_locked-behavior-on-compound-pages.patch
> page-flags-define-behavior-of-fs-io-related-flags-on-compound-pages.patch
> page-flags-define-behavior-of-lru-related-flags-on-compound-pages.patch

^^^ this one is fault, I think.

> page-flags-define-behavior-slb-related-flags-on-compound-pages.patch
> page-flags-define-behavior-of-xen-related-flags-on-compound-pages.patch
> page-flags-define-pg_reserved-behavior-on-compound-pages.patch
> page-flags-define-pg_swapbacked-behavior-on-compound-pages.patch
> page-flags-define-pg_swapcache-behavior-on-compound-pages.patch
> page-flags-define-pg_mlocked-behavior-on-compound-pages.patch
> page-flags-define-pg_uncached-behavior-on-compound-pages.patch
> page-flags-define-pg_uptodate-behavior-on-compound-pages.patch
> page-flags-look-on-head-page-if-the-flag-is-encoded-in-page-mapping.patch
> mm-sanitize-page-mapping-for-tail-pages.patch
> include-linux-page-flagsh-rename-macros-to-avoid-collisions.patch
> 
> Which one was the faulty patch?
> 
> > PageLRU() on tail pages now reports true if
> > head page is on LRU. It means no we can go futher insede
> > isolate_migratepages_block() with tail page.
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

-- 
 Kirill A. Shutemov

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2015-04-28 22:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-27 11:26 Kirill A. Shutemov
2015-04-27 11:50 ` Vlastimil Babka
2015-04-28 22:14 ` Andrew Morton
2015-04-28 22:28   ` Kirill A. Shutemov
2015-04-28 22:37     ` Andrew Morton
2015-04-28 22:44       ` Kirill A. Shutemov [this message]
2015-06-03  9:14         ` Vlastimil Babka
2015-06-03 11:24           ` Kirill A. Shutemov

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=20150428224442.GA6188@node.dhcp.inet.fi \
    --to=kirill@shutemov.name \
    --cc=akpm@linux-foundation.org \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=sasha.levin@oracle.com \
    --cc=vbabka@suse.cz \
    /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