From: Gordan Bobic <gordan@bobich.net>
To: kvm@vger.kernel.org
Subject: KSM For All Via LD_PRELOAD?
Date: Tue, 08 Jun 2010 19:43:07 +0100 [thread overview]
Message-ID: <4C0E8F3B.5060501@bobich.net> (raw)
Is this plausible?
I'm trying to work out if it's even worth considering this approach to
enable all memory used by in a system to be open to KSM page merging,
rather than only memory used by specific programs aware of it (e.g.
kvm/qemu).
Something like this would address the fact that container based
virtualization (OpenVZ, VServer, LXC) cannot benefit from KSM.
What I'm thinking about is somehow intercepting malloc() and wrapping it
so that all malloc()-ed memory gets madvise()-d as well.
Has this been done?
Or is this too crazy an idea?
Gordan
next reply other threads:[~2010-06-08 18:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-08 18:43 Gordan Bobic [this message]
2010-06-09 8:33 ` KSM For All Via LD_PRELOAD? Dor Laor
2010-06-09 8:56 ` Paolo Bonzini
2010-06-09 10:31 ` Gordan Bobic
2010-06-10 7:33 ` Dor Laor
2010-06-10 9:03 ` Gordan Bobic
2010-06-10 7:44 ` Jes Sorensen
2010-06-10 9:09 ` Gordan Bobic
2010-06-10 11:27 ` Jes Sorensen
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=4C0E8F3B.5060501@bobich.net \
--to=gordan@bobich.net \
--cc=kvm@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox