From: Mulyadi Santosa <mulyadi.santosa@gmail.com>
To: 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: Thu, 2 Jul 2020 15:29:18 +0700 [thread overview]
Message-ID: <CAGdaadbZES2x-JWdA3xFwk8wuu=bULd3X3775Se43ZSkWzFFLw@mail.gmail.com> (raw)
In-Reply-To: <CAAvDm6aumLxZdYPZxzhA+4a1LGuJS8+ui1cruE2eGwBxic11Hw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 917 bytes --]
On Tue, Jun 30, 2020 at 1:52 PM 孙世龙 sunshilong <sunshilong369@gmail.com>
wrote:
> Hi, list
> Is there some method or software that could purposely generate a lot
> of physical memory fragmentations on Linux?
>
> I need to do some tests under such circumstances.
>
> Thank you for your attention to this matter.
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies@kernelnewbies.org
> https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
Hi
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
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
[-- Attachment #1.2: Type: text/html, Size: 1698 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-02 8:31 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 [this message]
2020-07-03 4:58 ` Valdis Klētnieks
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='CAGdaadbZES2x-JWdA3xFwk8wuu=bULd3X3775Se43ZSkWzFFLw@mail.gmail.com' \
--to=mulyadi.santosa@gmail.com \
--cc=Kernelnewbies@kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).