From: William Lee Irwin III <wli@holomorphy.com>
To: HuaFeijun <hua.feijun@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: hugetlb bug
Date: Wed, 18 Jan 2006 00:37:10 -0800 [thread overview]
Message-ID: <20060118083710.GE13708@holomorphy.com> (raw)
In-Reply-To: <3fe1d240601180000n511f9697m@mail.gmail.com>
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.
Kernel versions for EM64T and ia64?
-- wli
next prev parent reply other threads:[~2006-01-18 8:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-18 8:00 hugetlb bug HuaFeijun
2006-01-18 8:37 ` William Lee Irwin III [this message]
2006-01-18 8:46 Zhang, Yanmin
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=20060118083710.GE13708@holomorphy.com \
--to=wli@holomorphy.com \
--cc=hua.feijun@gmail.com \
--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 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).