From: Wei Wang <wei.w.wang@intel.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
virtualization@lists.linux-foundation.org, mst@redhat.com,
mawilcox@microsoft.com, dave.hansen@intel.com,
akpm@linux-foundation.org, zhenwei.pi@youruncloud.com
Subject: Re: [PATCH] mm: don't zero ballooned pages
Date: Mon, 31 Jul 2017 16:34:58 +0800 [thread overview]
Message-ID: <597EEBB2.8080609@intel.com> (raw)
In-Reply-To: <20170731074350.GC15767@dhcp22.suse.cz>
On 07/31/2017 03:43 PM, Michal Hocko wrote:
> On Mon 31-07-17 15:41:49, Wei Wang wrote:
>> On 07/31/2017 02:55 PM, Michal Hocko wrote:
>>> On Mon 31-07-17 12:13:33, Wei Wang wrote:
>>>> Ballooned pages will be marked as MADV_DONTNEED by the hypervisor and
>>>> shouldn't be given to the host ksmd to scan.
>>> Could you point me where this MADV_DONTNEED is done, please?
>> Sure. It's done in the hypervisor when the balloon pages are received.
>>
>> Please see line 40 at
>> https://github.com/qemu/qemu/blob/master/hw/virtio/virtio-balloon.c
> Thanks. Are all hypervisors which are using this API doing this?
The implementation may be different across different hypervisors.
But the underlying concept is the same - they unmap the balloon
pages from the guest and those pages will be given to other guests
or host processes to use.
Regardless of the implementation, I think it is an improper operation
to make the memory KSM mergeable when the memory does not
belong to the guest anymore.
Best,
Wei
--
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: Wei Wang <wei.w.wang@intel.com>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
virtualization@lists.linux-foundation.org, mst@redhat.com,
mawilcox@microsoft.com, dave.hansen@intel.com,
akpm@linux-foundation.org, zhenwei.pi@youruncloud.com
Subject: Re: [PATCH] mm: don't zero ballooned pages
Date: Mon, 31 Jul 2017 16:34:58 +0800 [thread overview]
Message-ID: <597EEBB2.8080609@intel.com> (raw)
In-Reply-To: <20170731074350.GC15767@dhcp22.suse.cz>
On 07/31/2017 03:43 PM, Michal Hocko wrote:
> On Mon 31-07-17 15:41:49, Wei Wang wrote:
>> On 07/31/2017 02:55 PM, Michal Hocko wrote:
>>> On Mon 31-07-17 12:13:33, Wei Wang wrote:
>>>> Ballooned pages will be marked as MADV_DONTNEED by the hypervisor and
>>>> shouldn't be given to the host ksmd to scan.
>>> Could you point me where this MADV_DONTNEED is done, please?
>> Sure. It's done in the hypervisor when the balloon pages are received.
>>
>> Please see line 40 at
>> https://github.com/qemu/qemu/blob/master/hw/virtio/virtio-balloon.c
> Thanks. Are all hypervisors which are using this API doing this?
The implementation may be different across different hypervisors.
But the underlying concept is the same - they unmap the balloon
pages from the guest and those pages will be given to other guests
or host processes to use.
Regardless of the implementation, I think it is an improper operation
to make the memory KSM mergeable when the memory does not
belong to the guest anymore.
Best,
Wei
next prev parent reply other threads:[~2017-07-31 8:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-31 4:13 [PATCH] mm: don't zero ballooned pages Wei Wang
2017-07-31 4:13 ` Wei Wang
2017-07-31 6:55 ` Michal Hocko
2017-07-31 6:55 ` Michal Hocko
2017-07-31 7:39 ` ZhenweiPi
2017-07-31 7:39 ` ZhenweiPi
2017-07-31 7:39 ` ZhenweiPi
2017-07-31 7:41 ` Wei Wang
2017-07-31 7:41 ` Wei Wang
2017-07-31 7:41 ` Wei Wang
2017-07-31 7:43 ` Michal Hocko
2017-07-31 7:43 ` Michal Hocko
2017-07-31 8:34 ` Wei Wang [this message]
2017-07-31 8:34 ` Wei Wang
2017-07-31 8:34 ` Wei Wang
2017-07-31 7:43 ` Michal Hocko
2017-07-31 7:51 ` Michal Hocko
2017-07-31 7:51 ` Michal Hocko
2017-07-31 7:51 ` Michal Hocko
2017-07-31 8:23 ` ZhenweiPi
2017-07-31 8:37 ` Michal Hocko
2017-07-31 8:37 ` Michal Hocko
2017-07-31 8:37 ` Michal Hocko
2017-08-01 15:38 ` Michael S. Tsirkin
2017-08-01 15:38 ` Michael S. Tsirkin
2017-08-01 15:38 ` Michael S. Tsirkin
2017-07-31 8:23 ` ZhenweiPi
2017-07-31 6:55 ` Michal Hocko
-- strict thread matches above, loose matches on Subject: below --
2017-07-31 4:13 Wei Wang
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=597EEBB2.8080609@intel.com \
--to=wei.w.wang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=dave.hansen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mawilcox@microsoft.com \
--cc=mhocko@kernel.org \
--cc=mst@redhat.com \
--cc=virtualization@lists.linux-foundation.org \
--cc=zhenwei.pi@youruncloud.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 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.