2006-01-18 08:00:07

by HuaFeijun

[permalink] [raw]
Subject: hugetlb bug

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.


Attachments:
(No filename) (248.00 B)
meminfo (2.26 kB)
Download all attachments

2006-01-18 08:37:15

by William Lee Irwin III

[permalink] [raw]
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.

Kernel versions for EM64T and ia64?


-- wli

2006-01-18 08:47:09

by Zhang, Yanmin

[permalink] [raw]
Subject: RE: hugetlb bug

>>-----Original Message-----
>>From: [email protected] [mailto:[email protected]] On Behalf Of William Lee Irwin III
>>Sent: 2006??1??18?? 16:37
>>To: HuaFeijun
>>Cc: [email protected]
>>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.