- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Re: Tru64 5.1 kernel memory management.
Operating System - Tru64 Unix
1748282
Members
4033
Online
108761
Solutions
Forums
Categories
Company
Local Language
юдл
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
юдл
back
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
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
тАО05-11-2004 08:14 AM
тАО05-11-2004 08:14 AM
Tru64 5.1 kernel memory management.
Hi,
That prior messages was a mistake...
I'm having issues with the kernel memory allocator in Tru64 5.1 and IPFilter.
On a 96MB AlphaSTATION 433, I can load IPFilter without any problems. The exact same code compiled fails to load on a 256MB pc164 bsaed computer because of a 16k kernel memory bucket allocation failure.
The relevant line of output from "vmstat -M" is:
bkt elem_sz in_use el_free bytes fail_nowait
10 16384 3 4 49152 21
I've not tried to tune any kernel parameters, this is just the default setup.
Does anyone know what I need to do to fix this?
That prior messages was a mistake...
I'm having issues with the kernel memory allocator in Tru64 5.1 and IPFilter.
On a 96MB AlphaSTATION 433, I can load IPFilter without any problems. The exact same code compiled fails to load on a 256MB pc164 bsaed computer because of a 16k kernel memory bucket allocation failure.
The relevant line of output from "vmstat -M" is:
bkt elem_sz in_use el_free bytes fail_nowait
10 16384 3 4 49152 21
I've not tried to tune any kernel parameters, this is just the default setup.
Does anyone know what I need to do to fix this?
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2004 10:59 AM
тАО05-11-2004 10:59 AM
Re: Tru64 5.1 kernel memory management.
please don't interpret message, post it in original context. Is your message "vmunix: malloc failed: bucket size"?
If so the root cause of the problem could be: memory leak or wrong kernel parameters leading to an allocation problem.
For a starter use sys_check and correct the parameters marked within the output.
If so the root cause of the problem could be: memory leak or wrong kernel parameters leading to an allocation problem.
For a starter use sys_check and correct the parameters marked within the output.
Help() { FirstReadManual(urgently); Go_to_it;; }
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-11-2004 05:13 PM
тАО05-11-2004 05:13 PM
Re: Tru64 5.1 kernel memory management.
I'm with Ralf on this. Please start out with the exact (console?) message. Help us understand what made you worry about the 'kernel memory allocator'.
Good call on the: vmstat -M,
but maybe you over-reduced the output.
If a next reply is needed, please attach the full output as a .txt file (maintains formatting).
You can try increasing the map size (kmem_percent) and see if the problem goes away.
sysconfig -q generic kmem_percent ?
Good call on the: vmstat -M,
but maybe you over-reduced the output.
If a next reply is needed, please attach the full output as a .txt file (maintains formatting).
You can try increasing the map size (kmem_percent) and see if the problem goes away.
sysconfig -q generic kmem_percent ?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО05-12-2004 03:35 AM
тАО05-12-2004 03:35 AM
Re: Tru64 5.1 kernel memory management.
The output wasn't reduced (apart from vmstat -M): what's happening is MALLOC(9) is failing and there are no console messages from Mr vmunix.
The actual code does something like this:
MALLOC(foo, void *, 16376, M_TEMP, M_NOWAIT)
This should be ok, according to the man page for MALLOC(9). Changing it to pass M_WAITOK for size > 4k has fixed the problem.
But what I find strange is why a 96MB alpha works with M_NOWAIT and why the 256MB alpha didn't. Is the kmem allocator different for the two variants?
I suppose this is more a question for a forum related kernel (driver) development on Tru64 but I couldn't see one of those..
The actual code does something like this:
MALLOC(foo, void *, 16376, M_TEMP, M_NOWAIT)
This should be ok, according to the man page for MALLOC(9). Changing it to pass M_WAITOK for size > 4k has fixed the problem.
But what I find strange is why a 96MB alpha works with M_NOWAIT and why the 256MB alpha didn't. Is the kmem allocator different for the two variants?
I suppose this is more a question for a forum related kernel (driver) development on Tru64 but I couldn't see one of those..
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP