- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: kalloc() eat memory (3.0g)
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-14-2008 10:21 PM
08-14-2008 10:21 PM
kalloc() eat memory (3.0g)
Kernel TEXT pages not requested in crashconf
Will use an artificial mapping from a.out TEXT pages
Note: Consider P4_ELF_WARNING=2 to get more details
Note: No debug information for this module
kmeminfo (4.17)
unix: /stand/vmunix 11.23 64bit IA64
core: /dev/kmem live
link: Mon Oct 15 12:06:10 WSTDST 2007
boot: Fri Feb 22 19:02:43 2008
dump: Thu Aug 14 21:34:36 2008
----------------------------------------------------------------------
Pfdat processing:
Scanning 7045117 pfdat entries (be patient) ...
----------------------------------------------------------------------
Physical memory usage summary (in page/byte/percent):
Physmem = 7044912 26.9g 100% Physical memory
Freemem = 4937951 18.8g 70% Free physical memory
Used = 2106961 8.0g 30% Used physical memory
System = 2010095 7.7g 29% By kernel:
text = 6300 24.6m 0% text
data = 1477 5.8m 0% data
bss = 2342 9.1m 0% bss
Static = 187076 730.8m 3% for text/static data
Dynamic = 1104732 4.2g 16% for dynamic data
Bufcache = 704492 2.7g 10% for buffer cache
SCmem = 13795 53.9m 0% for critical memory
User = 101554 396.7m 1% By user processes:
Uarea = 9120 35.6m 0% for thread uareas
Disowned = 367 1.4m 0% Disowned pages
----------------------------------------------------------------------
Kernel dynamic memory usage (in page/byte/percent):
Physmem = 7044912 26.9g 100% Physical memory
Freemem = 4937951 18.8g 70% Free memory
Used = 2106961 8.0g 30% Used memory
Dynamic = 1104732 4.2g 16% Kernel dynamic memory
Arenas = 325408 1.2g 5% Kernel arenas
vx_global_pool = 46565 181.9m 1%
VFD_BT_NODE = 46016 179.8m 1%
spinlock = 29859 116.6m 0%
vm_pfn2v_arena = 27774 108.5m 0%
M_TEMP = 20572 80.4m 0%
vx_inode_cache = 20426 79.8m 0%
M_IOSYS = 14754 57.6m 0%
LVM_PBUF = 14411 56.3m 0%
region arena = 11980 46.8m 0%
ALLOCB_MBLK_LM = 10963 42.8m 0%
SWAP_MISC_ARENA = 9440 36.9m 0%
M_PREG = 9346 36.5m 0%
vx_buffer_cache = 7008 27.4m 0%
mdep arena = 5403 21.1m 0%
vx_rwsleeplock_ = 3895 15.2m 0%
Other = 46996 183.6m 1% Other arenas...
Kalloc = 779324 3.0g 11% kalloc()
SuperPagePool = 15786 61.7m 0% Kernel superpage cache
BufcacheBufs = 610544 2.3g 9% Buffer cache bufs
BufcacheHash = 16384 64.0m 0% Buffer cache hash heads
Other = 136610 533.6m 2% Other...
swapinfo -tm
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 18432 20 18412 0% 0 - 1 /dev/vg00/lvol2
reserve - 374 -374
memory 27519 6330 21189 23%
total 45951 6724 39227 15% - 0 -
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2008 05:49 AM
08-15-2008 05:49 AM
Re: kalloc() eat memory (3.0g)
What is it BufcacheBufs ?
How reduce memory consumption ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-15-2008 10:45 AM
08-15-2008 10:45 AM
Re: kalloc() eat memory (3.0g)
Why? What do you plan to use it for? You seem to have no memory pressure now. It would be more useful if you measure this when you are having problems.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2008 12:25 AM
08-22-2008 12:25 AM
Re: kalloc() eat memory (3.0g)
Mb Mb Mb PCT START/ Mb
TYPE AVAIL USED FREE USED LIMIT RESERVE PRI NAME
dev 18432 19 18413 0% 0 - 1 /dev/vg00/lvol2
reserve - 18413 -18413
memory 27519 26736 783 97%
total 45951 45168 783 98% - 0 -
]# ipcs -mpb
IPC status from /dev/kmem as of Fri Aug 22 12:21:03 2008
T ID KEY MODE OWNER GROUP SEGSZ CPID LPID
Shared Memory:
m 0 0x411c11da --rw-rw-rw- root root 348 584 584
m 1 0x4e0c0002 --rw-rw-rw- root root 61760 584 586
m 2 0x41201dc0 --rw-rw-rw- root root 8192 584 586
m 5931011 0xf78a4280 --rw-r----- oracle dba 11847065600 2510 15051
m 11698180 0x7a0c0002 --rw-rw-rw- oracle dba 1099904 2690 2690
ram 25G
oracle 11G
oracle user processes ~4G
filesystems cache 2.5G
free ~3G
hpux ~4G ??????
# /usr/contrib/Q4/bin/kmeminfo
Kernel TEXT pages not requested in crashconf
Will use an artificial mapping from a.out TEXT pages
Note: Consider P4_ELF_WARNING=2 to get more details
Note: No debug information for this module
kmeminfo (4.17)
unix: /stand/vmunix 11.23 64bit IA64
core: /dev/kmem live
link: Mon Oct 15 12:06:10 WSTDST 2007
boot: Fri Feb 22 19:02:46 2008
dump: Fri Aug 22 12:09:54 2008
----------------------------------------------------------------------
Pfdat processing:
Scanning 7045117 pfdat entries (be patient) ...
----------------------------------------------------------------------
Physical memory usage summary (in page/byte/percent):
Physmem = 7044912 26.9g 100% Physical memory
Freemem = 832673 3.2g 12% Free physical memory
Used = 6212239 23.7g 88% Used physical memory
System = 2043384 7.8g 29% By kernel:
text = 6300 24.6m 0% text
data = 1477 5.8m 0% data
bss = 2342 9.1m 0% bss
Static = 187076 730.8m 3% for text/static data
Dynamic = 1138021 4.3g 16% for dynamic data
Bufcache = 704492 2.7g 10% for buffer cache
SCmem = 13795 53.9m 0% for critical memory
User = 4174346 15.9g 59% By user processes:
Uarea = 23918 93.4m 0% for thread uareas
Clic = 364826 1.4g 5% for clic pages eg. locked async shm
Disowned = 367 1.4m 0% Disowned pages
----------------------------------------------------------------------
Kernel dynamic memory usage (in page/byte/percent):
Physmem = 7044912 26.9g 100% Physical memory
Freemem = 832673 3.2g 12% Free memory
Used = 6212239 23.7g 88% Used memory
Dynamic = 1138021 4.3g 16% Kernel dynamic memory
Arenas = 363239 1.4g 5% Kernel arenas
VFD_BT_NODE = 78346 306.0m 1%
vx_global_pool = 47336 184.9m 1%
spinlock = 29885 116.7m 0%
vm_pfn2v_arena = 27774 108.5m 0%
M_TEMP = 23034 90.0m 0%
vx_inode_cache = 20426 79.8m 0%
M_IOSYS = 14823 57.9m 0%
LVM_PBUF = 14411 56.3m 0%
region arena = 11980 46.8m 0%
ALLOCB_MBLK_LM = 10972 42.9m 0%
SWAP_MISC_ARENA = 9440 36.9m 0%
M_PREG = 9346 36.5m 0%
vx_buffer_cache = 9120 35.6m 0%
mdep arena = 5403 21.1m 0%
vx_rwsleeplock_ = 3895 15.2m 0%
Other = 47048 183.8m 1% Other arenas...
Kalloc = 774782 3.0g 11% kalloc()
SuperPagePool = 11121 43.4m 0% Kernel superpage cache
BufcacheBufs = 610544 2.3g 9% Buffer cache bufs
BufcacheHash = 16384 64.0m 0% Buffer cache hash heads
Other = 136733 534.1m 2% Other...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2008 01:49 AM
08-22-2008 01:49 AM
Re: kalloc() eat memory (3.0g)
Here is no memory issue, it will more easy to ans if you mention your Question more clearly.
Regards,
Gokul Chandola
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2008 02:34 AM
08-22-2008 02:34 AM
Re: kalloc() eat memory (3.0g)
>total 45951 45168 783 98%
Hmm, I would say now there is an issue.
It seems like more memory or more device swap should be added. Or you can try reducing the 2 Gb buffer cache.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2008 02:41 AM
08-22-2008 02:41 AM
Re: kalloc() eat memory (3.0g)
I ask why on my system Kalloc = 3.0g ?
What is it BufcacheBufs 2.3g ?
Kalloc = 774782 3.0g 11% kalloc()
SuperPagePool = 11121 43.4m 0% Kernel superpage cache
BufcacheBufs = 610544 2.3g 9% Buffer cache bufs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2008 03:13 AM
08-22-2008 03:13 AM
Re: kalloc() eat memory (3.0g)
>What is it BufcacheBufs 2.3g?
You can try to reduce the buffer cache, dbc_max_pct and dbc_min_pct. It is probably now 10%?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2008 03:28 AM
08-22-2008 03:28 AM
Re: kalloc() eat memory (3.0g)
# kctune -s dbc_min_pct=2
* The automatic 'backup' configuration has been updated.
* The requested changes have been applied to the currently
running system.
Tunable Value Expression Changes
dbc_min_pct (before) 5 Default Immed
(now) 2 2
# kctune -s dbc_max_pct=5
* The automatic 'backup' configuration has been updated.
* The requested changes have been applied to the currently
running system.
Tunable Value Expression Changes
dbc_max_pct (before) 10 10 Immed
(now) 5 5
# /usr/contrib/Q4/bin/kmeminfo
Kernel TEXT pages not requested in crashconf
Will use an artificial mapping from a.out TEXT pages
Note: Consider P4_ELF_WARNING=2 to get more details
Note: No debug information for this module
kmeminfo (4.17)
unix: /stand/vmunix 11.23 64bit IA64
core: /dev/kmem live
link: Mon Oct 15 12:06:10 WSTDST 2007
boot: Fri Feb 22 19:02:46 2008
dump: Fri Aug 22 15:23:00 2008
----------------------------------------------------------------------
Pfdat processing:
Scanning 7045117 pfdat entries (be patient) ...
----------------------------------------------------------------------
Physical memory usage summary (in page/byte/percent):
Physmem = 7044912 26.9g 100% Physical memory
Freemem = 1158141 4.4g 16% Free physical memory
Used = 5886771 22.5g 84% Used physical memory
System = 1690722 6.4g 24% By kernel:
text = 6300 24.6m 0% text
data = 1477 5.8m 0% data
bss = 2342 9.1m 0% bss
Static = 187076 730.8m 3% for text/static data
Dynamic = 1137605 4.3g 16% for dynamic data
Bufcache = 352246 1.3g 5% for buffer cache
SCmem = 13795 53.9m 0% for critical memory
User = 4197657 16.0g 60% By user processes:
Uarea = 23815 93.0m 0% for thread uareas
Clic = 364826 1.4g 5% for clic pages eg. locked async shm
Disowned = 367 1.4m 0% Disowned pages
----------------------------------------------------------------------
Kernel dynamic memory usage (in page/byte/percent):
Physmem = 7044912 26.9g 100% Physical memory
Freemem = 1158141 4.4g 16% Free memory
Used = 5886771 22.5g 84% Used memory
Dynamic = 1137605 4.3g 16% Kernel dynamic memory
Arenas = 362570 1.4g 5% Kernel arenas
VFD_BT_NODE = 78346 306.0m 1%
vx_global_pool = 47304 184.8m 1%
spinlock = 29885 116.7m 0%
vm_pfn2v_arena = 27774 108.5m 0%
M_TEMP = 23034 90.0m 0%
vx_inode_cache = 20426 79.8m 0%
M_IOSYS = 14825 57.9m 0%
LVM_PBUF = 14411 56.3m 0%
region arena = 11980 46.8m 0%
ALLOCB_MBLK_LM = 10972 42.9m 0%
SWAP_MISC_ARENA = 9440 36.9m 0%
M_PREG = 9346 36.5m 0%
vx_buffer_cache = 8480 33.1m 0%
mdep arena = 5403 21.1m 0%
vx_rwsleeplock_ = 3895 15.2m 0%
Other = 47049 183.8m 1% Other arenas...
Kalloc = 775035 3.0g 11% kalloc()
SuperPagePool = 11373 44.4m 0% Kernel superpage cache
BufcacheBufs = 610544 2.3g 9% Buffer cache bufs
BufcacheHash = 16384 64.0m 0% Buffer cache hash heads
Other = 136734 534.1m 2% Other...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
08-22-2008 04:53 AM
08-22-2008 04:53 AM
Re: kalloc() eat memory (3.0g)
Unless Don has an answer, you should be contacting the Response Center.