Until now we can't offline memory blocks which contain hugepages because
a hugepage is considered as an unmovable page. But now with this patch
series, a hugepage has become movable, so by using hugepage migration we
can offline such memory blocks.
What's different from other users of hugepage mig
On Wed, Jul 24, 2013 at 02:10:07PM +0800, Wanpeng Li wrote:
...
> >diff --git v3.11-rc1.orig/mm/page_isolation.c v3.11-rc1/mm/page_isolation.c
> >index 383bdbb..cf48ef6 100644
> >--- v3.11-rc1.orig/mm/page_isolation.c
> >+++ v3.11-rc1/mm/page_isolation.c
> >@@ -6,6 +6,7 @@
> > #include
> > #includ
On Fri, Jul 19, 2013 at 10:39 PM, Naoya Horiguchi
wrote:
> On Fri, Jul 19, 2013 at 01:40:38PM +0800, Hillf Danton wrote:
>> On Fri, Jul 19, 2013 at 5:34 AM, Naoya Horiguchi
>> wrote:
>> > @@ -518,9 +519,11 @@ static struct page *dequeue_huge_page_node(struct
>> > hstate *h, int nid)
>> > {
>> >
On Fri, Jul 19, 2013 at 01:40:38PM +0800, Hillf Danton wrote:
> On Fri, Jul 19, 2013 at 5:34 AM, Naoya Horiguchi
> wrote:
> > @@ -518,9 +519,11 @@ static struct page *dequeue_huge_page_node(struct
> > hstate *h, int nid)
> > {
> > struct page *page;
> >
> > - if (list_empty(&h->hug
On Fri, Jul 19, 2013 at 5:34 AM, Naoya Horiguchi
wrote:
> @@ -518,9 +519,11 @@ static struct page *dequeue_huge_page_node(struct hstate
> *h, int nid)
> {
> struct page *page;
>
> - if (list_empty(&h->hugepage_freelists[nid]))
> + list_for_each_entry(page, &h->hugepage_freeli
Until now we can't offline memory blocks which contain hugepages because
a hugepage is considered as an unmovable page. But now with this patch
series, a hugepage has become movable, so by using hugepage migration we
can offline such memory blocks.
What's different from other users of hugepage mig
6 matches
Mail list logo
