From: Rich Felker <dalias@libc.org>
To: musl@lists.openwall.com
Subject: Re: application frequently map and unmap memory
Date: Tue, 2 Aug 2016 12:18:39 -0400 [thread overview]
Message-ID: <20160802161839.GU15995@brightrain.aerifal.cx> (raw)
In-Reply-To: <CAAKbDrehn7q4G6H0moU65quPZY+nxTVrwgzPA2tJ=pamUeBpZQ@mail.gmail.com>
On Mon, Aug 01, 2016 at 06:06:29PM -0400, Yuxin Ren wrote:
> Hi all,
>
> Are there any applications that stress the memory mapping and unmapping utility
> (It frequently map and unmap memory)?
Are you looking for real-world applications with this type of load? Or
artificial stress tests? I would not expect to find many of the former
since these are costly operations and there are usually better ways to
do whatever is needed. The latter should be easy to write if needed,
though.
Rich
next prev parent reply other threads:[~2016-08-02 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 22:06 Yuxin Ren
2016-08-02 16:18 ` Rich Felker [this message]
2016-08-02 16:58 ` Yuxin Ren
2016-08-02 17:36 ` John Levine
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=20160802161839.GU15995@brightrain.aerifal.cx \
--to=dalias@libc.org \
--cc=musl@lists.openwall.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/musl/
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).