From: Wanpeng Li <liwanp@linux.vnet.ibm.com>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: Minchan Kim <minchan@kernel.org>, Mel Gorman <mgorman@suse.de>,
Andrew Morton <akpm@linux-foundation.org>,
riel@redhat.com, aquini@redhat.com, linux-mm@kvack.org,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: skip the page buddy block instead of one page
Date: Thu, 15 Aug 2013 19:23:32 +0800 [thread overview]
Message-ID: <20130815112331.GA26134@hacker.(null)> (raw)
In-Reply-To: <520CB84D.6000306@huawei.com>
On Thu, Aug 15, 2013 at 07:15:25PM +0800, Xishi Qiu wrote:
>On 2013/8/15 17:51, Wanpeng Li wrote:
>
>> On Thu, Aug 15, 2013 at 03:45:11PM +0800, Xishi Qiu wrote:
>>> On 2013/8/15 12:24, Minchan Kim wrote:
>>>
>>>>> Please read full thread in detail.
>>>>>
>>>>> Mel suggested following as
>>>>>
>>>>> if (PageBuddy(page)) {
>>>>> int nr_pages = (1 << page_order(page)) - 1;
>>>>> if (PageBuddy(page)) {
>>>>> nr_pages = min(nr_pages, MAX_ORDER_NR_PAGES - 1);
>>>>> low_pfn += nr_pages;
>>>>> continue;
>>>>> }
>>>>> }
>>>>>
>>>>> min(nr_pages, xxx) removes your concern but I think Mel's version
>>>>> isn't right. It should be aligned with pageblock boundary so I
>>>>> suggested following.
>>>>>
>>>>> if (PageBuddy(page)) {
>>>>> #ifdef CONFIG_MEMORY_ISOLATION
>>>>> unsigned long order = page_order(page);
>>>>> if (PageBuddy(page)) {
>>>>> low_pfn += (1 << order) - 1;
>>>>> low_pfn = min(low_pfn, end_pfn);
>>>>> }
>>>>> #endif
>>>>> continue;
>>>>> }
>>>>>
>>>
>>> Hi Minchan,
>>>
>>> I understand now, but why use "end_pfn" here?
>>> Maybe like this:
>>>
>>> if (PageBuddy(page)) {
>>> /*
>>> * page_order is racy without zone->lock but worst case
>>> * by the racing is just skipping pageblock_nr_pages.
>>> */
>>> unsigned long nr_pages = 1 << page_order(page);
>>> if (likely(PageBuddy(page))) {
>>> nr_pages = min(nr_pages, MAX_ORDER_NR_PAGES);
>>
>> How much sense it make? nr_pages is still equal to itself since nr_pages can't
>> larger than MAX_ORDER_NR_PAGES.
>>
>
>Hi Wanpeng,
>
>Mel pointed "page_order cannot be used unless zone->lock is held".
>"Even if the page is still page buddy, there is no guarantee that it's
>the same page order as the first read. It could have be currently merging
>with adjacent buddies for example."
>
>If someone use the page during the double PageBuddy check, the value
>of private may be wrong. In my opinion, just keep the code unchanged.
>
Hi Xishi,
You miss my point, I mean nr_pages = min(nr_pages, MAX_ORDER_NR_PAGES); not
make sense since nr_pages can't larger then MAX_ORDER_NR_PAGES.
Regards,
Wanpeng Li
>Thanks,
>Xishi Qiu
>
>>>
>>> /* Align with pageblock boundary */
>>> if ((low_pfn & (pageblock_nr_pages - 1)) + nr_pages >
>>> pageblock_nr_pages)
>>> low_pfn = ALIGN(low_pfn + 1, pageblock_nr_pages) - 1;
>>> else
>>> low_pfn += nr_pages - 1;
>>> }
>>> continue;
>>> }
>>>
>>> Thanks,
>>> Xishi Qiu
>>>
>>>>> so worst case is (pageblock_nr_pages - 1).
>>>>> but we don't need to add CONFIG_MEMORY_ISOLATION so my suggestion
>>>>> is following as.
>>>>>
>>>>> if (PageBuddy(page)) {
>>>>> unsigned long order = page_order(page);
>>>>> if (PageBuddy(page)) {
>>>>> low_pfn += (1 << order) - 1;
>>>>> low_pfn = min(low_pfn, end_pfn);
>>>>
>>>> Maybe it should be low_pfn = min(low_pfn, end_pfn - 1).
>>>>
>>>>
>>>>> }
>>>>> continue;
>>>>> }
>>>>>
>
>
--
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>
next prev parent reply other threads:[~2013-08-15 11:23 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-14 4:45 [PATCH] mm: skip the page buddy block instead of one page Xishi Qiu
2013-08-14 7:07 ` Minchan Kim
2013-08-14 8:57 ` Mel Gorman
2013-08-14 9:14 ` Xishi Qiu
2013-08-14 15:52 ` Minchan Kim
2013-08-14 16:16 ` Mel Gorman
2013-08-14 16:39 ` Minchan Kim
2013-08-14 18:00 ` Mel Gorman
2013-08-14 19:11 ` Minchan Kim
2013-08-15 2:32 ` Xishi Qiu
2013-08-15 2:44 ` Minchan Kim
2013-08-15 3:46 ` Xishi Qiu
2013-08-15 3:59 ` Wanpeng Li
2013-08-15 3:59 ` Wanpeng Li
2013-08-15 4:17 ` Minchan Kim
2013-08-15 4:24 ` Minchan Kim
2013-08-15 7:45 ` Xishi Qiu
2013-08-15 9:51 ` Wanpeng Li
2013-08-15 9:51 ` Wanpeng Li
2013-08-15 11:15 ` Xishi Qiu
2013-08-15 11:23 ` Wanpeng Li
2013-08-15 11:23 ` Wanpeng Li [this message]
2013-08-15 11:17 ` Xishi Qiu
2013-08-15 6:38 ` Xishi Qiu
2013-08-15 11:30 ` Mel Gorman
2013-08-15 13:19 ` Minchan Kim
2013-08-15 13:42 ` Mel Gorman
2013-08-15 14:16 ` Minchan Kim
2013-08-14 20:26 ` Andrew Morton
2013-08-14 22:22 ` Mel Gorman
2014-01-17 14:32 ` [PATCH] mm: Improve documentation of page_order Mel Gorman
2014-01-17 18:40 ` Rafael Aquini
2014-01-17 18:53 ` Laura Abbott
2014-01-17 19:59 ` Mel Gorman
2014-01-21 11:05 ` [PATCH] mm: Improve documentation of page_order v2 Mel Gorman
2014-01-20 6:12 ` [PATCH] mm: Improve documentation of page_order Minchan Kim
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='20130815112331.GA26134@hacker.(null)' \
--to=liwanp@linux.vnet.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=aquini@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=minchan@kernel.org \
--cc=qiuxishi@huawei.com \
--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 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).