From: Randy Dunlap <randy.dunlap@oracle.com>
To: Nish Aravamudan <nish.aravamudan@gmail.com>
Cc: Zan Lynx <zlynx@acm.org>, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.22-rc1-mm1 huge pages VM freeze (maybe?)
Date: Wed, 01 Aug 2007 08:54:45 -0700 [thread overview]
Message-ID: <46B0ACC5.6010904@oracle.com> (raw)
In-Reply-To: <29495f1d0708010845x446f7823qcfe2c5244b604078@mail.gmail.com>
Nish Aravamudan wrote:
> On 7/31/07, Randy Dunlap <randy.dunlap@oracle.com> wrote:
>> On Tue, 31 Jul 2007 15:44:21 -0600 Zan Lynx wrote:
>>
>>> I was playing with huge pages and libhugetlbfs. Small programs like
>>> "ls" work fine. I tried running Evolution through libhugetlbfs and the
>>> system slowly stops running. One interesting thing is the "ps" command,
>>> it gets stuck like this:
>> Do you mean 2.6.22-rc1-mm1 or 2.6.23-rc1-mm1?
>>
>> There was a hugepage problem fixed very recently, in 2.6.23-rc1 IIRC.
>
> Actually fixed just after 2.6.23-rc1:
>
> git describe 5ab3ee7b1cd5c91eb2272764f9d7d1fe4749681e
> v2.6.23-rc1-14-g5ab3ee7
Looks to me like Andrew included Ken's patch in his rc1-mm1 anyway,
so that shouldn't be the issue. Or did I not read mm/hugetlb.c correctly?
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2007-08-01 15:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 21:44 2.6.22-rc1-mm1 huge pages VM freeze (maybe?) Zan Lynx
2007-07-31 22:02 ` Randy Dunlap
2007-07-31 22:01 ` Zan Lynx
2007-08-01 15:47 ` Nish Aravamudan
2007-08-01 15:52 ` Nish Aravamudan
2007-08-02 1:40 ` Zan Lynx
2007-08-03 3:51 ` Nish Aravamudan
2007-08-01 21:41 ` Nish Aravamudan
2007-08-01 15:45 ` Nish Aravamudan
2007-08-01 15:54 ` Randy Dunlap [this message]
2007-08-01 15:52 ` Nish Aravamudan
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=46B0ACC5.6010904@oracle.com \
--to=randy.dunlap@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nish.aravamudan@gmail.com \
--cc=zlynx@acm.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