From: Xishi Qiu <qiuxishi@huawei.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Vlastimil Babka <vbabka@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>,
iamjoonsoo.kim@lge.com, alexander.h.duyck@redhat.com,
sasha.levin@oracle.com, Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: add the block to the tail of the list in expand()
Date: Wed, 5 Aug 2015 15:54:26 +0800 [thread overview]
Message-ID: <55C1C132.2010805@huawei.com> (raw)
In-Reply-To: <55C0CBC3.2000602@intel.com>
On 2015/8/4 22:27, Dave Hansen wrote:
> On 08/03/2015 06:13 PM, Xishi Qiu wrote:
>> How did you do the experiment?
>
> I just stuck in some counters in expand() that looked to see whether the
> list was empty or not when the page is added and then printed them out
> occasionally.
>
Hi Dave,
I add some debug code like this, but it doesn't trigger the dump_stack().
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -834,6 +834,12 @@ static inline void expand(struct zone *zone, struct page *page,
continue;
}
#endif
+
+ if (!list_empty(&area->free_list[migratetype])) {
+ printk("expand(), the list is not empty\n");
+ dump_stack();
+ }
+
list_add(&page[size].lru, &area->free_list[migratetype]);
area->nr_free++;
set_page_order(&page[size], high);
> It will be interesting to see the results both on a freshly-booted
> system and one that's reached relatively steady-state and is moving
> around a minimal number of pageblocks between the different types.
>
> In any case, the end result here needs to be some indication that the
> patch either helps ease fragmentation or helps performance.
>
> .
>
--
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: Xishi Qiu <qiuxishi@huawei.com>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@suse.de>, Vlastimil Babka <vbabka@suse.cz>,
Johannes Weiner <hannes@cmpxchg.org>,
Michal Hocko <mhocko@suse.cz>, <iamjoonsoo.kim@lge.com>,
<alexander.h.duyck@redhat.com>, <sasha.levin@oracle.com>,
Linux MM <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: add the block to the tail of the list in expand()
Date: Wed, 5 Aug 2015 15:54:26 +0800 [thread overview]
Message-ID: <55C1C132.2010805@huawei.com> (raw)
In-Reply-To: <55C0CBC3.2000602@intel.com>
On 2015/8/4 22:27, Dave Hansen wrote:
> On 08/03/2015 06:13 PM, Xishi Qiu wrote:
>> How did you do the experiment?
>
> I just stuck in some counters in expand() that looked to see whether the
> list was empty or not when the page is added and then printed them out
> occasionally.
>
Hi Dave,
I add some debug code like this, but it doesn't trigger the dump_stack().
--- a/mm/page_alloc.c
+++ b/mm/page_alloc.c
@@ -834,6 +834,12 @@ static inline void expand(struct zone *zone, struct page *page,
continue;
}
#endif
+
+ if (!list_empty(&area->free_list[migratetype])) {
+ printk("expand(), the list is not empty\n");
+ dump_stack();
+ }
+
list_add(&page[size].lru, &area->free_list[migratetype]);
area->nr_free++;
set_page_order(&page[size], high);
> It will be interesting to see the results both on a freshly-booted
> system and one that's reached relatively steady-state and is moving
> around a minimal number of pageblocks between the different types.
>
> In any case, the end result here needs to be some indication that the
> patch either helps ease fragmentation or helps performance.
>
> .
>
next prev parent reply other threads:[~2015-08-05 8:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-31 9:30 [PATCH] mm: add the block to the tail of the list in expand() Xishi Qiu
2015-07-31 9:30 ` Xishi Qiu
2015-07-31 23:24 ` Dave Hansen
2015-07-31 23:24 ` Dave Hansen
2015-08-03 2:05 ` Xishi Qiu
2015-08-03 2:05 ` Xishi Qiu
2015-08-03 4:10 ` Dave Hansen
2015-08-03 4:10 ` Dave Hansen
2015-08-04 1:13 ` Xishi Qiu
2015-08-04 1:13 ` Xishi Qiu
2015-08-04 14:27 ` Dave Hansen
2015-08-04 14:27 ` Dave Hansen
2015-08-05 7:54 ` Xishi Qiu [this message]
2015-08-05 7:54 ` Xishi Qiu
2015-08-05 14:47 ` Dave Hansen
2015-08-05 14:47 ` Dave Hansen
2015-08-14 7:55 ` Xishi Qiu
2015-08-14 7:55 ` Xishi Qiu
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=55C1C132.2010805@huawei.com \
--to=qiuxishi@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@redhat.com \
--cc=dave.hansen@intel.com \
--cc=hannes@cmpxchg.org \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mhocko@suse.cz \
--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 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.