From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Mulyadi Santosa <mulyadi.santosa@gmail.com>
Cc: kernelnewbies <Kernelnewbies@kernelnewbies.org>
Subject: Re: Is there some method or software that could purposely generate a lot of physical memory fragmentations on linux?
Date: Fri, 03 Jul 2020 00:58:37 -0400 [thread overview]
Message-ID: <6499.1593752317@turing-police> (raw)
In-Reply-To: <CAGdaadbZES2x-JWdA3xFwk8wuu=bULd3X3775Se43ZSkWzFFLw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 577 bytes --]
On Thu, 02 Jul 2020 15:29:18 +0700, Mulyadi Santosa said:
> Just pseudo idea, if this is in user space, try to: allocate many blocks
> of memory using malloc, each having different size, keep the returned
> pointer, then randomly free() some of them, then malloc() again with
> different size
That will cause userspace malloc() to have fragmentation, but as far
as the kernel is concerned it's all just 4K pages of user memory.
Causing physical memory fragmentation will require abusing the kernel
memory allocators such as kmalloc() and vmalloc() and friends.
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2020-07-03 4:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 6:51 Is there some method or software that could purposely generate a lot of physical memory fragmentations on linux? 孙世龙 sunshilong
2020-07-02 8:29 ` Mulyadi Santosa
2020-07-03 4:58 ` Valdis Klētnieks [this message]
2020-07-03 5:20 ` 孙世龙 sunshilong
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=6499.1593752317@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=Kernelnewbies@kernelnewbies.org \
--cc=mulyadi.santosa@gmail.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).