All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Mel Gorman <mel@csn.ul.ie>, Rik van Riel <riel@redhat.com>,
	Sasha Levin <levinsasha928@gmail.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	jaschut@sandia.gov, kamezawa.hiroyu@jp.fujitsu.com,
	Dave Jones <davej@redhat.com>
Subject: Re: [PATCH -mm v2] mm: have order > 0 compaction start off where it left
Date: Wed, 4 Jul 2012 00:42:19 -0700	[thread overview]
Message-ID: <20120704004219.47d0508d.akpm@linux-foundation.org> (raw)
In-Reply-To: <4FF3ABA1.3070808@kernel.org>

On Wed, 04 Jul 2012 11:34:09 +0900 Minchan Kim <minchan@kernel.org> wrote:

> > The rest of this patch takes care to ensure that
> > ->compact_cached_free_pfn is aligned to pageblock_nr_pages.  But it now
> > appears that this particular site will violate that.
> > 
> > What's up?  Do we need to fix this site, or do we remove all that
> > make-compact_cached_free_pfn-aligned code?
> 
> 
> I vote removing the warning because it doesn't related to Rik's incremental compaction.
> Let's see. 
> 
> high_pfn = min(low_pfn, pfn) = cc->migrate_pfn + pageblock_nr_pages.
> In here, cc->migrate_pfn isn't necessarily pageblock aligined.
> So if we don't consider compact_cached_free_pfn, it can hit.
> 
> static void isolate_freepages()
> {
> 	high_pfn = min(low_pfn, pfn) = cc->migrate_pfn + pageblock_nr_pages;
> 	for (..) {
> 		...
> 		 WARN_ON_ONCE(high_pfn & (pageblock_nr_pages - 1));
> 		
> 	}
> }

Please, look at the patch.  In numerous places it is aligning
compact_cached_free_pfn to a multiple of pageblock_nr_pages.  But in
one place it doesn't do that.  So are all those alignment operations
necessary?

--
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>

WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Minchan Kim <minchan@kernel.org>
Cc: Mel Gorman <mel@csn.ul.ie>, Rik van Riel <riel@redhat.com>,
	Sasha Levin <levinsasha928@gmail.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	jaschut@sandia.gov, kamezawa.hiroyu@jp.fujitsu.com,
	Dave Jones <davej@redhat.com>
Subject: Re: [PATCH -mm v2] mm: have order > 0 compaction start off where it left
Date: Wed, 4 Jul 2012 00:42:19 -0700	[thread overview]
Message-ID: <20120704004219.47d0508d.akpm@linux-foundation.org> (raw)
In-Reply-To: <4FF3ABA1.3070808@kernel.org>

On Wed, 04 Jul 2012 11:34:09 +0900 Minchan Kim <minchan@kernel.org> wrote:

> > The rest of this patch takes care to ensure that
> > ->compact_cached_free_pfn is aligned to pageblock_nr_pages.  But it now
> > appears that this particular site will violate that.
> > 
> > What's up?  Do we need to fix this site, or do we remove all that
> > make-compact_cached_free_pfn-aligned code?
> 
> 
> I vote removing the warning because it doesn't related to Rik's incremental compaction.
> Let's see. 
> 
> high_pfn = min(low_pfn, pfn) = cc->migrate_pfn + pageblock_nr_pages.
> In here, cc->migrate_pfn isn't necessarily pageblock aligined.
> So if we don't consider compact_cached_free_pfn, it can hit.
> 
> static void isolate_freepages()
> {
> 	high_pfn = min(low_pfn, pfn) = cc->migrate_pfn + pageblock_nr_pages;
> 	for (..) {
> 		...
> 		 WARN_ON_ONCE(high_pfn & (pageblock_nr_pages - 1));
> 		
> 	}
> }

Please, look at the patch.  In numerous places it is aligning
compact_cached_free_pfn to a multiple of pageblock_nr_pages.  But in
one place it doesn't do that.  So are all those alignment operations
necessary?


  reply	other threads:[~2012-07-04  7:40 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 17:55 [PATCH -mm v2] mm: have order > 0 compaction start off where it left Rik van Riel
2012-06-28 17:55 ` Rik van Riel
2012-06-28 20:19 ` Jim Schutt
2012-06-28 20:19   ` Jim Schutt
2012-06-28 20:57   ` Rik van Riel
2012-06-28 20:57     ` Rik van Riel
2012-06-28 20:59 ` Andrew Morton
2012-06-28 20:59   ` Andrew Morton
2012-06-28 21:24   ` Rik van Riel
2012-06-28 21:24     ` Rik van Riel
2012-06-28 21:35     ` Andrew Morton
2012-06-28 21:35       ` Andrew Morton
2012-07-02 17:42       ` Sasha Levin
2012-07-02 17:42         ` Sasha Levin
2012-07-03  0:57         ` Rik van Riel
2012-07-03  0:57           ` Rik van Riel
2012-07-03  2:54           ` Minchan Kim
2012-07-03  2:54             ` Minchan Kim
2012-07-03 10:10           ` Mel Gorman
2012-07-03 10:10             ` Mel Gorman
2012-07-03 21:48             ` Andrew Morton
2012-07-03 21:48               ` Andrew Morton
2012-07-04  2:34               ` Minchan Kim
2012-07-04  2:34                 ` Minchan Kim
2012-07-04  7:42                 ` Andrew Morton [this message]
2012-07-04  7:42                   ` Andrew Morton
2012-07-04  8:01                   ` Minchan Kim
2012-07-04  8:01                     ` Minchan Kim
2012-07-11 20:18                     ` [PATCH -mm v3] " Rik van Riel
2012-07-11 20:18                       ` Rik van Riel
2012-07-12  2:26                       ` Minchan Kim
2012-07-12  2:26                         ` Minchan Kim
2012-07-04  9:57                   ` [PATCH -mm v2] " Mel Gorman
2012-07-04  9:57                     ` Mel Gorman
2012-06-28 23:27 ` Minchan Kim
2012-06-28 23:27   ` Minchan Kim
2012-07-03 14:59   ` Rik van Riel
2012-07-03 14:59     ` Rik van Riel
2012-07-04  2:28     ` Minchan Kim
2012-07-04  2:28       ` Minchan Kim
2012-07-04 10:08       ` Mel Gorman
2012-07-04 10:08         ` Mel Gorman
2012-07-03 20:13   ` [PATCH -mm] mm: minor fixes for compaction Rik van Riel
2012-07-03 20:13     ` Rik van Riel
2012-07-04  2:36     ` Minchan Kim
2012-07-04  2:36       ` Minchan Kim
2012-06-29 10:02 ` [PATCH -mm v2] mm: have order > 0 compaction start off where it left Mel Gorman
2012-06-29 10:02   ` Mel Gorman
2012-06-30  3:51 ` Kamezawa Hiroyuki
2012-06-30  3:51   ` Kamezawa Hiroyuki

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=20120704004219.47d0508d.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=davej@redhat.com \
    --cc=jaschut@sandia.gov \
    --cc=kamezawa.hiroyu@jp.fujitsu.com \
    --cc=levinsasha928@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mel@csn.ul.ie \
    --cc=minchan@kernel.org \
    --cc=riel@redhat.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.