Bug 816055

Summary: Document 3GB Memory Allocation limit on 32-bit systems
Product: Red Hat Enterprise MRG Reporter: Leonid Zhaldybin <lzhaldyb>
Component: Messaging_Programming_ReferenceAssignee: Joshua Wulf <jwulf>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: DevelopmentCC: astitcher, esammons, jskeoch, lcarlon
Target Milestone: 2.2   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-09-20 03:13:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Leonid Zhaldybin 2012-04-25 07:25:58 UTC 
Description of problem:
Apparently, 32-bit broker is unable to allocate more than ~3GB of memory, which is not a bug but an obvious restriction (see bug 756790). Nevertheless, this restriction is not mentioned in the user documentation.

  
Actual results:
Memory allocation restriction for 32-bit broker is not described in the MRG documentation.

Expected results:
Memory allocation restriction for 32-bit broker is described properly in the documentation.

Additional info:
Comment 1 Joshua Wulf 2012-05-01 09:12:42 UTC 
http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_MRG/2.2/html-single/Messaging_Installation_and_Configuration_Guide/index.html#Memory_Allocation_Limit_32_bit
Comment 3 Andrew Stitcher 2012-07-31 14:08:00 UTC 
I think the user process memory limit depends on what kind of kernel you are running: a regular 32 bit kernel will only allow a user process to allocate 3Gb (because 1Gb of memory space is reserved for the kernel itself). However I think a PAE kernel will allow a user process to allocate the full 4Gb of memory space. Because in that case the kernel run in its own memory space (but there is a heavier penalty paid for switching from user to kernel mode).

Also note that the 3Gb limit includes all queues and internal data for the qpid broker as well as all of the program code and libraries used so that substantially less than 3Gb would be available for a single queue.
Comment 4 Cheryn Tan 2012-09-20 02:54:15 UTC 
Released for MRG 2.2