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:
Post your ideas
Start by posting ideas and requests to this portal to enhance a Power product or service. Take a look at ideas others have posted and upvote them if they matter to you,
Post an idea
Upvote ideas and add comments to ideas that matter most to you
Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The Power teams will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notification on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Specific link you will want to bookmark for future use
IBM Unified Ideas Portal-https://ideas.ibm.com/- Use this site to create or search for existing Ideas across all IBM products that are outside of Power, and track all of your personal interactions with all Ideas.
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.
Do not place IBM confidential, company confidential, or personal information into any field.