From: starlight@binnacle.cx
To: Adam Litke <agl@us.ibm.com>, Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, bugme-daemon@bugzilla.kernel.org,
Andy Whitcroft <apw@shadowen.org>
Subject: Re: [Bug 12134] New: can't shmat() 1GB hugepage segment from second process more than one time
Date: Tue, 02 Dec 2008 14:41:56 -0500 [thread overview]
Message-ID: <6.2.5.6.2.20081202143914.01ddcd88@binnacle.cx> (raw)
In-Reply-To: <1228245880.13482.19.camel@localhost.localdomain>
I'll collect a more detailed picture in the next day or so and
send the info. Maybe create a test-case.
Several other segments 128MB are created before the 1GB segment.
They all run in the 0x300000000 range on 256MB boundaries
(second digit changes) and the big one goes at 0x400000000.
'mlockall()' is called periodically as well--perhaps
that's the antagonist.
Have SHM_HUGETLB set even for no-create attaches, which I'm not
sure is proper. It works on RHEL though.
Memory is touched in each segment, 100% for the smaller
ones and small % for the big one. Didn't think it made
any difference since it's all locked by implication.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2008-12-02 19:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-12134-27@http.bugzilla.kernel.org/>
2008-12-02 2:14 ` Andrew Morton
2008-12-02 19:24 ` Adam Litke
2008-12-02 19:41 ` starlight [this message]
2008-12-04 3:15 ` starlight
2008-12-05 17:17 ` Adam Litke
2008-12-05 17:49 ` starlight
2008-12-05 18:57 ` Adam Litke
2008-12-05 19:04 ` starlight
2008-12-06 5:17 starlight
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=6.2.5.6.2.20081202143914.01ddcd88@binnacle.cx \
--to=starlight@binnacle.cx \
--cc=agl@us.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.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