From: "Michael S. Tsirkin" <mst@redhat.com>
To: "shesha Sreenivasamurthy (shesha)" <shesha@cisco.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: Unlinking hugepage backing file after initialiation
Date: Tue, 29 Sep 2015 19:16:28 +0300 [thread overview]
Message-ID: <20150929161628.GA3810@redhat.com> (raw)
In-Reply-To: <D22FFFC5.22271%shesha@cisco.com>
On Tue, Sep 29, 2015 at 03:48:08PM +0000, shesha Sreenivasamurthy (shesha) wrote:
> If huge pages are allocated for the guest and if the guest crashes there may be
> a chance that the new guest may not be able to get huge pages again as some
> other guest or process on the host used it. But I am not able to understand
> memory corruption you are talking about. In my opinion, if a process using a
> piece of memory goes away, it should not re-attach to the same piece of memory
> without running a sanity check on it.
guest memory is allocated an freed by hypervisor, right?
I don't think it's dpdk's job.
--
MST
next prev parent reply other threads:[~2015-09-29 16:16 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 0:04 Unlinking hugepage backing file after initialiation shesha Sreenivasamurthy (shesha)
2015-09-29 2:37 ` Xie, Huawei
2015-09-29 15:15 ` Xie, Huawei
2015-09-29 15:48 ` shesha Sreenivasamurthy (shesha)
2015-09-29 16:16 ` Michael S. Tsirkin [this message]
2015-09-29 17:50 ` shesha Sreenivasamurthy (shesha)
2015-09-29 21:35 ` Michael S. Tsirkin
2015-09-30 21:44 ` shesha Sreenivasamurthy (shesha)
2015-09-30 21:53 ` Ananyev, Konstantin
2015-09-30 22:04 ` shesha Sreenivasamurthy (shesha)
2015-10-01 8:41 ` Bruce Richardson
2015-10-05 13:08 ` Xie, Huawei
2015-10-05 20:20 ` Michael S. Tsirkin
2015-10-12 8:46 ` Xie, Huawei
2015-09-29 9:03 ` Ananyev, Konstantin
2015-09-29 11:14 ` Bruce Richardson
2015-09-29 14:03 ` shesha Sreenivasamurthy (shesha)
-- strict thread matches above, loose matches on Subject: below --
2015-09-29 0:24 shesha Sreenivasamurthy (shesha)
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=20150929161628.GA3810@redhat.com \
--to=mst@redhat.com \
--cc=dev@dpdk.org \
--cc=shesha@cisco.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.