Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
1.) max_map_count
Defines the maximum number of memory map areas that a process may use. In most cases, the default value of 65536 is appropriate. When is it not appropriate?
Some large applications need to mmap() more than 65536 files. If this is the case appplication will fail the mmap so the sysadmin should increase max_map_count by doubling its current value.
2.) aio-max-nr
This parameter is not in the deployment guide. Is it supported?
Yes, aio-max-nr is still set to 65536 by default and still defines the maximum allowed number of events in all active asynchronous I/O contexts.
Larry
1.) max_map_count Defines the maximum number of memory map areas that a process may use. In most cases, the default value of 65536 is appropriate. When is it not appropriate? Some large applications need to mmap() more than 65536 files. If this is the case appplication will fail the mmap so the sysadmin should increase max_map_count by doubling its current value. 2.) aio-max-nr This parameter is not in the deployment guide. Is it supported? Yes, aio-max-nr is still set to 65536 by default and still defines the maximum allowed number of events in all active asynchronous I/O contexts. Larry