This portal is to open public enhancement requests against IBM Power Systems products, including IBM i. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
See this idea on ideas.ibm.com
As discussed in the Support case TS008099503, the ISV would like to be able to specify not only DATAPSIZE, TEXTPSIZE and STACKPSIZE as a linker option but also allow SHMPSIZE to be specified.
Currently, if you build an application which should use 64K pages to improve runtime performance, you can set the LDR_CNTRL at runtime to "DATAPSIZE=64K@TEXTPSIZE=64K@STACKPSIZE=64K@SHMPSIZE=64K".
Setting the environment variable before starting the application is a user action that is often times 'forgotten' - leading to degraded performance of the application.
As an alternative, the use of 64K pages can be built-in the application by specifying it as a linker option.
But currently, the linker only accepts 64K page sizes to be specified for data, text and stack. To get the full performance benefit of 64K pages, the end user who runs the application still needs to set LDR_CNTRL such that SHMPSIZE is also set to 64K.
This idea is about adding a 'shmpsize' option to the linker which would allow to set 64K page size at link time.
If an application is then build with 64K for data/text/stack/shm sizes, it would come with the full 64K page size exploitation out-of-the-box, without the user having to worry about setting an addtl. environment variable.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
excellent idea and another task removed by implementing this so it works straight out of the box