All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk>
To: "Kunal Trivedi" <ktrivedi@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Possible Bug in VM accounting (Committed_AS) on x86_64 architecture ?
Date: Wed, 29 Nov 2006 21:04:08 +0000	[thread overview]
Message-ID: <20061129210408.3ea5800a@localhost.localdomain> (raw)
In-Reply-To: <63a95c50611291129q109abeb2o7e5afb7ca94a3f2c@mail.gmail.com>

> I have noticed that 64 bit machine with overcommit policy (as above)
> starts giving problem within 3-4 weeks. To prove that I've written
> small program.

The older RHEL kernels had some cases that didn't quite account exactly
but current ones ought to be right - for Centos I'd expect similar but
ask there not here as it is a very old and branched away kernel.

>  It allocates memory of different sizes (not that it matters much due
> to caching of diffeent malloc. I am using standard ptmalloc). Sizes
> are 16B, 32B, 64B, 256B, 1024B, 57B, 127B and so on... . Then it
> touches that memory (memset) and then free it. These operations are
> being performed in while(1) loop.

I would expect that, it's fragmentation. The real test is whether the
values go back properly when you kill the program.

  reply	other threads:[~2006-11-29 20:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <63a95c50611291122l27c9af6fha78db3bf32fe6c1c@mail.gmail.com>
2006-11-29 19:29 ` Possible Bug in VM accounting (Committed_AS) on x86_64 architecture ? Kunal Trivedi
2006-11-29 21:04   ` Alan [this message]
2006-12-07  7:26 Kunal Trivedi

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=20061129210408.3ea5800a@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=ktrivedi@gmail.com \
    --cc=linux-kernel@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.