All of lore.kernel.org
 help / color / mirror / Atom feed
From: Pintu Agarwal <pintu_agarwal@yahoo.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Eric Dumazet <eric.dumazet@gmail.com>
Cc: "Changli Gao" <xiaosuo@gmail.com>,
	"Américo Wang" <xiyou.wangcong@gmail.com>,
	"Jiri Slaby" <jslaby@suse.cz>, azurIt <azurit@pobox.sk>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org, "Jiri Slaby" <jirislaby@gmail.com>
Subject: Regarding memory fragmentation using malloc....
Date: Tue, 12 Apr 2011 23:54:05 -0700 (PDT)	[thread overview]
Message-ID: <530486.50523.qm@web162020.mail.bf1.yahoo.com> (raw)
In-Reply-To: <1302662256.2811.27.camel@edumazet-laptop>

Dear All,

I am trying to understand how memory fragmentation occurs in linux using many malloc calls.
I am trying to reproduce the page fragmentation problem in linux 2.6.29.x on a linux mobile(without Swap) using a small malloc(in loop) test program of BLOCK_SIZE (64*(4*K)).
And then monitoring the page changes in /proc/buddyinfo after each operation.
>From the output I can see that the page values under buddyinfo keeps changing. But I am not able to relate these changes with my malloc BLOCK_SIZE.
I mean with my BLOCK_SIZE of (2^6 x 4K ==> 2^6 PAGES) the 2^6 th block under /proc/buddyinfo should change. But this is not the actual behaviour.
Whatever is the blocksize, the buddyinfo changes only for 2^0 or 2^1 or 2^2 or 2^3.

I am trying to measure the level of fragmentation after each page allocation.
Can somebody explain me in detail, how actually /proc/buddyinfo changes after each allocation and deallocation.


Thanks,
Pintu



      

WARNING: multiple messages have this Message-ID (diff)
From: Pintu Agarwal <pintu_agarwal@yahoo.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Eric Dumazet <eric.dumazet@gmail.com>
Cc: "Changli Gao" <xiaosuo@gmail.com>,
	"Américo Wang" <xiyou.wangcong@gmail.com>,
	"Jiri Slaby" <jslaby@suse.cz>, azurIt <azurit@pobox.sk>,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org, "Jiri Slaby" <jirislaby@gmail.com>
Subject: Regarding memory fragmentation using malloc....
Date: Tue, 12 Apr 2011 23:54:05 -0700 (PDT)	[thread overview]
Message-ID: <530486.50523.qm@web162020.mail.bf1.yahoo.com> (raw)
In-Reply-To: <1302662256.2811.27.camel@edumazet-laptop>

Dear All,

I am trying to understand how memory fragmentation occurs in linux using many malloc calls.
I am trying to reproduce the page fragmentation problem in linux 2.6.29.x on a linux mobile(without Swap) using a small malloc(in loop) test program of BLOCK_SIZE (64*(4*K)).
And then monitoring the page changes in /proc/buddyinfo after each operation.
>From the output I can see that the page values under buddyinfo keeps changing. But I am not able to relate these changes with my malloc BLOCK_SIZE.
I mean with my BLOCK_SIZE of (2^6 x 4K ==> 2^6 PAGES) the 2^6 th block under /proc/buddyinfo should change. But this is not the actual behaviour.
Whatever is the blocksize, the buddyinfo changes only for 2^0 or 2^1 or 2^2 or 2^3.

I am trying to measure the level of fragmentation after each page allocation.
Can somebody explain me in detail, how actually /proc/buddyinfo changes after each allocation and deallocation.


Thanks,
Pintu





--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

  reply	other threads:[~2011-04-13  6:54 UTC|newest]

Thread overview: 98+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-15 13:25 Regression from 2.6.36 azurIt
2011-03-17  0:15 ` Greg KH
2011-03-17  0:53   ` Dave Jones
2011-03-17 13:30     ` azurIt
2011-04-07 10:01   ` azurIt
2011-04-07 10:19     ` Jiri Slaby
2011-04-07 10:19       ` Jiri Slaby
2011-04-07 10:19       ` Jiri Slaby
2011-04-07 11:21       ` Américo Wang
2011-04-07 11:21         ` Américo Wang
2011-04-07 11:57         ` Eric Dumazet
2011-04-07 11:57           ` Eric Dumazet
2011-04-07 11:57           ` Eric Dumazet
2011-04-07 12:13           ` Eric Dumazet
2011-04-07 12:13             ` Eric Dumazet
2011-04-07 12:13             ` Eric Dumazet
2011-04-07 15:27             ` Changli Gao
2011-04-07 15:36               ` Eric Dumazet
2011-04-07 15:36                 ` Eric Dumazet
2011-04-07 15:36                 ` Eric Dumazet
2011-04-12 22:49                 ` Andrew Morton
2011-04-12 22:49                   ` Andrew Morton
2011-04-13  1:23                   ` Changli Gao
2011-04-13  1:23                     ` Changli Gao
2011-04-13  1:31                     ` Andrew Morton
2011-04-13  1:31                       ` Andrew Morton
2011-04-13  2:37                       ` Eric Dumazet
2011-04-13  2:37                         ` Eric Dumazet
2011-04-13  2:37                         ` Eric Dumazet
2011-04-13  6:54                         ` Pintu Agarwal [this message]
2011-04-13  6:54                           ` Regarding memory fragmentation using malloc Pintu Agarwal
2011-04-13 11:44                           ` Américo Wang
2011-04-13 11:44                             ` Américo Wang
2011-04-13 13:56                             ` Pintu Agarwal
2011-04-13 13:56                               ` Pintu Agarwal
2011-04-13 15:25                               ` Michal Nazarewicz
2011-04-13 15:25                                 ` Michal Nazarewicz
2011-04-14  6:44                                 ` Pintu Agarwal
2011-04-14  6:44                                   ` Pintu Agarwal
2011-04-14 10:47                                   ` Michal Nazarewicz
2011-04-14 10:47                                     ` Michal Nazarewicz
2011-04-14 12:24                                     ` Pintu Agarwal
2011-04-14 12:24                                       ` Pintu Agarwal
2011-04-14 12:31                                       ` Michal Nazarewicz
2011-04-14 12:31                                         ` Michal Nazarewicz
2011-04-13 21:16                         ` Regression from 2.6.36 Andrew Morton
2011-04-13 21:16                           ` Andrew Morton
2011-04-13 21:24                           ` Andrew Morton
2011-04-13 21:24                           ` Andrew Morton
2011-04-13 21:24                             ` Andrew Morton
2011-04-19 19:29                             ` azurIt
2011-04-19 19:29                               ` azurIt
2011-04-19 19:55                               ` Andrew Morton
2011-04-19 19:55                                 ` Andrew Morton
2011-04-13 21:44                           ` David Rientjes
2011-04-13 21:44                             ` David Rientjes
2011-04-13 21:54                             ` Andrew Morton
2011-04-13 21:54                               ` Andrew Morton
2011-04-14  2:10                           ` Eric Dumazet
2011-04-14  2:10                             ` Eric Dumazet
2011-04-14  2:10                             ` Eric Dumazet
2011-04-14  5:28                             ` Andrew Morton
2011-04-14  5:28                               ` Andrew Morton
2011-04-14  6:31                               ` Eric Dumazet
2011-04-14  6:31                                 ` Eric Dumazet
2011-04-14  6:31                                 ` Eric Dumazet
2011-04-14  9:08                                 ` azurIt
2011-04-14  9:08                                   ` azurIt
2011-04-14 10:27                                   ` Eric Dumazet
2011-04-14 10:27                                     ` Eric Dumazet
2011-04-14 10:27                                     ` Eric Dumazet
2011-04-14 10:31                                     ` azurIt
2011-04-14 10:31                                       ` azurIt
2011-04-14 10:31                                       ` azurIt
2011-04-14 10:25                           ` Mel Gorman
2011-04-15  9:59                             ` azurIt
2011-04-15  9:59                               ` azurIt
2011-04-15  9:59                               ` azurIt
2011-04-15 10:47                               ` Mel Gorman
2011-04-15 10:47                                 ` Mel Gorman
2011-04-15 10:56                                 ` azurIt
2011-04-15 10:56                                   ` azurIt
2011-04-15 10:56                                   ` azurIt
2011-04-15 11:17                                   ` Mel Gorman
2011-04-15 11:17                                     ` Mel Gorman
2011-04-15 11:36                                     ` azurIt
2011-04-15 11:36                                       ` azurIt
2011-04-15 11:36                                       ` azurIt
2011-04-15 13:01                                       ` Mel Gorman
2011-04-15 13:01                                         ` Mel Gorman
2011-04-15 13:21                                         ` azurIt
2011-04-15 13:21                                           ` azurIt
2011-04-15 13:21                                           ` azurIt
2011-04-15 14:15                                           ` Mel Gorman
2011-04-15 14:15                                             ` Mel Gorman
2011-04-08 12:25               ` azurIt
2011-04-08 12:25                 ` azurIt
2011-04-08 12:25                 ` azurIt

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=530486.50523.qm@web162020.mail.bf1.yahoo.com \
    --to=pintu_agarwal@yahoo.com \
    --cc=akpm@linux-foundation.org \
    --cc=azurit@pobox.sk \
    --cc=eric.dumazet@gmail.com \
    --cc=jirislaby@gmail.com \
    --cc=jslaby@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=xiaosuo@gmail.com \
    --cc=xiyou.wangcong@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.