linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marcelo Tosatti <marcelo.tosatti@cyclades.com>
To: akpm@osdl.org, Hugh Dickins <hugh@veritas.com>
Cc: linux-mm@kvack.org
Subject: visual representation of swap area allocation
Date: Wed, 25 May 2005 12:59:25 -0300	[thread overview]
Message-ID: <20050525155925.GA16874@logos.cnet> (raw)

[-- Attachment #1: Type: text/plain, Size: 897 bytes --]


Hi,

Due to personal interest, I've hacked up a small program to generate a 
visual representation of swap area allocation. Results are quite
interesting to me, so I've decided to share them with you.

Test program is memtest's "fillmem" (on a 512/512 mem/swap machine).

kernel is 2.6.11-rc4.

stock_second_stage.png: stock allocator after fillmem's first stage
akpm_first_stage.png: akpm's
stock_first_stage.png: stock allocator after fillmem's second stage
akpm_second_stage.png: akpm's

"Legend": 
White: free
Red: used
Black: past end of area

I wonder about the noticeable periodic white regions on akpm's allocator,
my guess is that its due to "properties" of the hash function. Collisions 
could explain that ? Note there is a matching red region for each white 
region. 

There is no noticeable performance difference between the two allocators 
with the "fillmem" workload on my tests.

[-- Attachment #2: akpm_first_stage.png --]
[-- Type: image/png, Size: 2008 bytes --]

[-- Attachment #3: akpm_second_stage.png --]
[-- Type: image/png, Size: 2246 bytes --]

[-- Attachment #4: stock_first_stage.png --]
[-- Type: image/png, Size: 526 bytes --]

[-- Attachment #5: stock_second_stage.png --]
[-- Type: image/png, Size: 1705 bytes --]

                 reply	other threads:[~2005-05-25 15:59 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20050525155925.GA16874@logos.cnet \
    --to=marcelo.tosatti@cyclades.com \
    --cc=akpm@osdl.org \
    --cc=hugh@veritas.com \
    --cc=linux-mm@kvack.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