mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gurudas Pai <gurudas.pai@oracle.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [BUG]:2.6.25-rc7 memory leak with hugepages.
Date: Thu, 27 Mar 2008 15:54:05 +0530	[thread overview]
Message-ID: <47EB75C5.20207@oracle.com> (raw)
In-Reply-To: <20080327083849.GF15626@elte.hu>



Ingo Molnar wrote:
> * Gurudas Pai <gurudas.pai@oracle.com> wrote:
> 
>> Hi,
>>
>> On 2.6.25-rc7 allocate hugepages and run a fio test with following 
>> jobfile,
> 
> could you try x86.git/latest:
> 
>   http://people.redhat.com/mingo/x86.git/README
> 
> it has a fix that could fix such a leak.
> 
> 	Ingo

Applied latest two patches and re-ran the test,

hugetlb: fix potential livelock in return_unused_surplus_hugepages()
hugetlb: indicate surplus huge page counts in per-node meminfo

Still same result,

>cat /proc/meminfo | grep Huge
HugePages_Total:  1000
HugePages_Free:    551
HugePages_Rsvd:      1
HugePages_Surp:      0
Hugepagesize:     2048 kB

>echo 0 > /proc/sys/vm/nr_hugepages
>cat /proc/meminfo | grep Huge
HugePages_Total:   450
HugePages_Free:      1
HugePages_Rsvd:      1
HugePages_Surp:    450
Hugepagesize:     2048 kB



Thanks,
-Guru

  reply	other threads:[~2008-03-27 10:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-27  7:35 Gurudas Pai
2008-03-27  8:38 ` Ingo Molnar
2008-03-27 10:24   ` Gurudas Pai [this message]
2008-04-04  3:40     ` Nish Aravamudan
2008-04-04  7:28       ` Nish Aravamudan
2008-04-04  7:45         ` Gurudas Pai
2008-04-04  7:48       ` Gurudas Pai
2008-04-04 17:16       ` Andy Whitcroft
2008-04-04 17:31         ` [PATCH] hugetlbpage.txt: correct overcommit caveat [Was Re: [BUG]:2.6.25-rc7 memory leak with hugepages.] Nishanth Aravamudan
2008-04-04 18:04           ` Nishanth Aravamudan
2008-04-04 18:11           ` Andy Whitcroft

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=47EB75C5.20207@oracle.com \
    --to=gurudas.pai@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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
Powered by JetHome