From: Soichiro Ueda <the.latticeheart@gmail.com>
To: David Hildenbrand <david@redhat.com>,
mst@redhat.com, jasowang@redhat.com, akpm@linux-foundation.org
Cc: virtualization@lists.linux-foundation.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
kalutes@google.com, mhiramat@kernel.org, cwd@google.com
Subject: Re: [PATCH] virtio_balloon: high order allocation
Date: Thu, 29 Dec 2022 14:31:48 +0900 [thread overview]
Message-ID: <444735fd-7076-7bd3-dc5e-7135a7f3a95c@gmail.com> (raw)
In-Reply-To: <c8ea7076-f107-c340-6b34-6b22a9369da5@redhat.com>
Hi David.
> How does this affect page migration / balloon compaction etc?
I guess this patch doesn't affect balloon compaction. When allocating
pages using alloc_pages(), it skips compaction by masking out
__GFP_RECLAIM if the order is larger than 0.
As for page migration, in the current implementation it migrate a
0-order page to another 0-order page. With this patch, it may migrate a
high-order page to another same-order page.
But I noticed that the migrated high-order page is handled as 0-order
page in virtballoon_migratepage().
> balloon_page_insert(vb_dev_info, newpage);
We should put the newpage into a page list of the corresponding order,
like this.
balloon_page_enqueue(vb_dev_info, newpage, order);
I'll fix it in the v2 patch.
Thank you,
next prev parent reply other threads:[~2022-12-29 5:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 9:35 [PATCH] virtio_balloon: high order allocation Soichiro Ueda
2022-12-23 9:40 ` David Hildenbrand
2022-12-23 9:40 ` David Hildenbrand
2022-12-29 5:31 ` Soichiro Ueda [this message]
2023-01-02 11:55 ` David Hildenbrand
2023-01-02 11:55 ` David Hildenbrand
2022-12-24 3:26 ` Liu Shixin
2022-12-29 6:27 ` Soichiro Ueda
2022-12-23 21:04 kernel test robot
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=444735fd-7076-7bd3-dc5e-7135a7f3a95c@gmail.com \
--to=the.latticeheart@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cwd@google.com \
--cc=david@redhat.com \
--cc=jasowang@redhat.com \
--cc=kalutes@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhiramat@kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.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 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.