All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sean Neakums <sneakums@zork.net>
To: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 2.5.66: task_struct memory leak?
Date: Tue, 25 Mar 2003 16:11:32 +0000	[thread overview]
Message-ID: <6usmtbe897.fsf@zork.zork.net> (raw)
In-Reply-To: <20030325155104.B24418@flint.arm.linux.org.uk> (Russell King's message of "Tue, 25 Mar 2003 15:51:04 +0000")

commence  Russell King quotation:

> I'm seeing memory disappear at a rate of 8K / process, which seems to
> suggest that the ARM level 1 page tables aren't getting freed either.
>
> Is anyone seeing this type of behaviour on x86?

Running 2.5.66 (plus Ingo Molnar's sched-2.5.66-A2), and I don't seem
to see a growth in the task_struct slab after repeated forking:

$ grep task_struct /proc/slabinfo ; for i in $(seq 1000) ; do /bin/true ; done ; grep task_struct /proc/slabinfo
task_struct           79     80   1552   16   16    2 :   54   27
task_struct           79     80   1552   16   16    2 :   54   27

-- 
Sean Neakums - <sneakums@zork.net>

      reply	other threads:[~2003-03-25 16:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-25 15:51 2.5.66: task_struct memory leak? Russell King
2003-03-25 16:11 ` Sean Neakums [this message]

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=6usmtbe897.fsf@zork.zork.net \
    --to=sneakums@zork.net \
    --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.