Kernel Newbies archive on lore.kernel.org
 help / color / Atom feed
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
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

  reply index

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-30  6:51 孙世龙 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

Kernel Newbies archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kernelnewbies/0 kernelnewbies/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kernelnewbies kernelnewbies/ https://lore.kernel.org/kernelnewbies \
		kernelnewbies@kernelnewbies.org
	public-inbox-index kernelnewbies

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernelnewbies.kernelnewbies


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git