From: "shesha Sreenivasamurthy (shesha)" <shesha@cisco.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [dpdk-dev] Unlinking hugepage backing file after initialiation
Date: Wed, 30 Sep 2015 21:44:29 +0000 [thread overview]
Message-ID: <D2316BA4.22470%shesha@cisco.com> (raw)
In-Reply-To: <20150930003531-mutt-send-email-mst@redhat.com>
What I heard is the following: A multi-process DPDK application, working either in master-worker or master-slave fashion, can potentially benefit by keeping the backing files in hugetlbfs. However, it is does not work today as the pages are cleaned and added back when the application restarts. On the other hand, for a single process application there is actually no benefit keeping the pages around.
Therefore, I was wondering if we can make this configurable by passing a command line argument that will either unlink or keep the backing files.
--
- Thanks
char * (*shesha) (uint64_t cache, uint8_t F00D)
{ return 0x0000C0DE; }
From: "Michael S. Tsirkin" <mst@redhat.com<mailto:mst@redhat.com>>
Date: Tuesday, September 29, 2015 at 2:35 PM
To: Cisco Employee <shesha@cisco.com<mailto:shesha@cisco.com>>
Cc: "Xie, Huawei" <huawei.xie@intel.com<mailto:huawei.xie@intel.com>>, "dev@dpdk.org<mailto:dev@dpdk.org>" <dev@dpdk.org<mailto:dev@dpdk.org>>
Subject: Re: [dpdk-dev] Unlinking hugepage backing file after initialiation
On Tue, Sep 29, 2015 at 05:50:00PM +0000, shesha Sreenivasamurthy (shesha) wrote:
Sure. Then, is there any real reason why the backing files should not be
unlinked ?
AFAIK qemu unlinks them already.
--
MST
next prev parent reply other threads:[~2015-09-30 21:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 0:04 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
2015-09-29 17:50 ` shesha Sreenivasamurthy (shesha)
2015-09-29 21:35 ` Michael S. Tsirkin
2015-09-30 21:44 ` shesha Sreenivasamurthy (shesha) [this message]
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)
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=D2316BA4.22470%shesha@cisco.com \
--to=shesha@cisco.com \
--cc=dev@dpdk.org \
--cc=mst@redhat.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).