From: "Zhang, Yanmin" <yanmin.zhang@intel.com>
To: "William Lee Irwin III" <wli@holomorphy.com>,
"HuaFeijun" <hua.feijun@gmail.com>
Cc: <linux-kernel@vger.kernel.org>
Subject: RE: hugetlb bug
Date: Wed, 18 Jan 2006 16:46:34 +0800 [thread overview]
Message-ID: <8126E4F969BA254AB43EA03C59F44E840483E8D4@pdsmsx404> (raw)
>>-----Original Message-----
>>From: linux-kernel-owner@vger.kernel.org [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of William Lee Irwin III
>>Sent: 2006年1月18日 16:37
>>To: HuaFeijun
>>Cc: linux-kernel@vger.kernel.org
>>Subject: Re: hugetlb bug
>>
>>On Wed, Jan 18, 2006 at 04:00:03PM +0800, HuaFeijun wrote:
>>> Is it kernel bug? The code works normally on ia64 machine,howerver, on
>>> EM64T,it fails tot work.
>>> The function call of shmat will change /proc/meminfo;and the shmdt
>>> can't restore it to original content. How to restore it to original
>>> stauts?Thanks.
>>> Is it kernel bug? The code works normally on ia64 machine,howerver,
>>> on EM64T,it fails tot work. The function call of shmat will change
>>> /proc/meminfo file's content;and the shmdt can't restore the file's
>>> content. How to restore it to original stauts?Thanks.
Did you check ipc? Command 'ipcs -a" could show all shared memory. I guess you app doesn't call shmctl(..., IPC_RMID, ...) after shmdt. Use ipcrm to release them manually.
next reply other threads:[~2006-01-18 8:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 8:46 Zhang, Yanmin [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-18 8:00 hugetlb bug HuaFeijun
2006-01-18 8:37 ` William Lee Irwin III
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=8126E4F969BA254AB43EA03C59F44E840483E8D4@pdsmsx404 \
--to=yanmin.zhang@intel.com \
--cc=hua.feijun@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/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;
as well as URLs for NNTP newsgroup(s).