All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Mosberger <davidm@napali.hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: [Linux-ia64] munmap() slowness
Date: Wed, 05 Mar 2003 23:45:24 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105590709805980@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105590709805979@msgid-missing>

>>>>> On Wed, 5 Mar 2003 17:30:01 -0600, Andy Isaacson <adi@hexapodia.org> said:

  Andy> munmap on a 15TB anonymous area is extremely slow on our Itanium 2 box.
  Andy> #include <sys/mman.h>
  Andy> int main(void) {
  Andy> size_t s = 1024*1024*1024*1024L * 15;
  Andy> munmap(mmap(0, s, PROT_READ|PROT_WRITE,
  Andy> MAP_NORESERVE|MAP_PRIVATE|MAP_ANONYMOUS, -1, 0),
  Andy> s);
  Andy> return 0;
  Andy> }

  Andy> ./a.out 0.00s user 1.51s system 100% cpu 1.515 total

  Andy> The kernel is 2.4.19 plus linux-2.4.19-ia64-020821.diff.gz (plus some
  Andy> local changes that shouldn't be relevant).

  Andy> Of course this isn't a real app, but I thought this was an interesting
  Andy> result.

  Andy> Please CC me on any replies, as I am not subscribed to the list.

$ uname -r
2.4.19-mckinley-smp
$ /usr/bin/time ./a.out
0.00user 0.00system 0:00.00elapsed 100%CPU (0avgtext+0avgdata 0maxresident)k
0inputs+0outputs (44major+13minor)pagefaults 0swaps

strace output says:

mmap(NULL, 16492674416640, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_NORESERVE, -1, 0) = 0x20000000002b4000
munmap(0x20000000002b4000, 16492674416640) = 0

Seems to perform just fine.

	--david


  reply	other threads:[~2003-03-05 23:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-05 23:30 [Linux-ia64] munmap() slowness Andy Isaacson
2003-03-05 23:45 ` David Mosberger [this message]
2003-03-06  0:24 ` Andy Isaacson

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=marc-linux-ia64-105590709805980@msgid-missing \
    --to=davidm@napali.hpl.hp.com \
    --cc=linux-ia64@vger.kernel.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 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.