linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Mel Gorman <mel@csn.ul.ie>,
	jaschut@sandia.gov, minchan@kernel.org,
	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: Mon, 02 Jul 2012 20:57:03 -0400	[thread overview]
Message-ID: <4FF2435F.2070302@redhat.com> (raw)
In-Reply-To: <1341250950.16969.6.camel@lappy>

On 07/02/2012 01:42 PM, Sasha Levin wrote:
> On Thu, 2012-06-28 at 14:35 -0700, Andrew Morton wrote:
>> On Thu, 28 Jun 2012 17:24:25 -0400 Rik van Riel<riel@redhat.com>  wrote:
>>>
>>>>> @@ -463,6 +474,8 @@ static void isolate_freepages(struct zone *zone,
>>>>>              */
>>>>>             if (isolated)
>>>>>                     high_pfn = max(high_pfn, pfn);
>>>>> +          if (cc->order>   0)
>>>>> +                  zone->compact_cached_free_pfn = high_pfn;
>>>>
>>>> Is high_pfn guaranteed to be aligned to pageblock_nr_pages here?  I
>>>> assume so, if lots of code in other places is correct but it's
>>>> unobvious from reading this function.
>>>
>>> Reading the code a few more times, I believe that it is
>>> indeed aligned to pageblock size.
>>
>> I'll slip this into -next for a while.
>>
>> --- a/mm/compaction.c~isolate_freepages-check-that-high_pfn-is-aligned-as-expected
>> +++ a/mm/compaction.c
>> @@ -456,6 +456,7 @@ static void isolate_freepages(struct zon
>>                  }
>>                  spin_unlock_irqrestore(&zone->lock, flags);
>>
>> +               WARN_ON_ONCE(high_pfn&  (pageblock_nr_pages - 1));
>>                  /*
>>                   * Record the highest PFN we isolated pages from. When next
>>                   * looking for free pages, the search will restart here as
>
> I've triggered the following with today's -next:

I've been staring at the migrate code for most of the afternoon,
and am not sure how this is triggered.

At this point, I'm going to focus my attention on addressing
Minchan's comments on my code, and hoping someone who is more
familiar with the migrate code knows how high_pfn ends up
being not pageblock_nr_pages aligned...

-- 
All rights reversed

--
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:[~2012-07-03  0:57 UTC|newest]

Thread overview: 25+ 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 20:19 ` Jim Schutt
2012-06-28 20:57   ` Rik van Riel
2012-06-28 20:59 ` Andrew Morton
2012-06-28 21:24   ` Rik van Riel
2012-06-28 21:35     ` Andrew Morton
2012-07-02 17:42       ` Sasha Levin
2012-07-03  0:57         ` Rik van Riel [this message]
2012-07-03  2:54           ` Minchan Kim
2012-07-03 10:10           ` Mel Gorman
2012-07-03 21:48             ` Andrew Morton
2012-07-04  2:34               ` Minchan Kim
2012-07-04  7:42                 ` Andrew Morton
2012-07-04  8:01                   ` Minchan Kim
2012-07-11 20:18                     ` [PATCH -mm v3] " Rik van Riel
2012-07-12  2:26                       ` Minchan Kim
2012-07-04  9:57                   ` [PATCH -mm v2] " Mel Gorman
2012-06-28 23:27 ` Minchan Kim
2012-07-03 14:59   ` Rik van Riel
2012-07-04  2:28     ` Minchan Kim
2012-07-04 10:08       ` Mel Gorman
2012-07-03 20:13   ` [PATCH -mm] mm: minor fixes for compaction Rik van Riel
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-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=4FF2435F.2070302@redhat.com \
    --to=riel@redhat.com \
    --cc=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 \
    /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).