All of lore.kernel.org
 help / color / mirror / Atom feed
From: HuaFeijun <hua.feijun@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: hugetlb bug
Date: Wed, 18 Jan 2006 16:00:03 +0800	[thread overview]
Message-ID: <3fe1d240601180000n511f9697m@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 253 bytes --]

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.

[-- Attachment #2: meminfo --]
[-- Type: text/plain, Size: 2310 bytes --]

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.
-------------------------------------------------------
=== before shmat ===
MemTotal:      2056388 kB
MemFree:        607300 kB
Buffers:         43976 kB
Cached:         134252 kB
SwapCached:          0 kB
Active:         151940 kB
Inactive:        63436 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2056388 kB
LowFree:        607300 kB
SwapTotal:     4096564 kB
SwapFree:      4096564 kB
Dirty:             176 kB
Writeback:           0 kB
Mapped:          50880 kB
Slab:            93236 kB
Committed_AS:    90340 kB
PageTables:       3528 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264436 kB
VmallocChunk: 536606243 kB
HugePages_Total:   500
HugePages_Free:    500
Hugepagesize:     2048 kB

=== after shmat ===
MemTotal:      2056388 kB
MemFree:        607300 kB
Buffers:         43976 kB
Cached:         134252 kB
SwapCached:          0 kB
Active:         151940 kB
Inactive:        63436 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2056388 kB
LowFree:        607300 kB
SwapTotal:     4096564 kB
SwapFree:      4096564 kB
Dirty:             176 kB
Writeback:           0 kB
Mapped:          50880 kB
Slab:            93236 kB
Committed_AS:    90340 kB
PageTables:       3528 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264436 kB
VmallocChunk: 536606243 kB
HugePages_Total:   500
HugePages_Free:    0
Hugepagesize:     2048 kB

=== after shmdt===
MemTotal:      2056388 kB
MemFree:        607300 kB
Buffers:         43976 kB
Cached:         134252 kB
SwapCached:          0 kB
Active:         151940 kB
Inactive:        63436 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      2056388 kB
LowFree:        607300 kB
SwapTotal:     4096564 kB
SwapFree:      4096564 kB
Dirty:             176 kB
Writeback:           0 kB
Mapped:          50880 kB
Slab:            93236 kB
Committed_AS:    90340 kB
PageTables:       3528 kB
VmallocTotal: 536870911 kB
VmallocUsed:    264436 kB
VmallocChunk: 536606243 kB
HugePages_Total:   500
HugePages_Free:    0
Hugepagesize:     2048 kB

             reply	other threads:[~2006-01-18  8:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-18  8:00 HuaFeijun [this message]
2006-01-18  8:37 ` hugetlb bug William Lee Irwin III
  -- strict thread matches above, loose matches on Subject: below --
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=3fe1d240601180000n511f9697m@mail.gmail.com \
    --to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.