IBM Power Ideas Portal


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).


Shape the future of IBM!

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:

Search existing ideas

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 your ideas

  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

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.

Add a new idea Subscribe
Status Not under consideration
Workspace AIX
Created by Guest
Created on Nov 30, 2017

RELATED IDEAS

Frame work design for vmgetinfo called from WPAR

I reviewed all the available data and examined the AIX code of the vmgetinfo() system call, called from a WPAR. It is true that vmgetinfo() call, called from global returns quicker than vmgetinfo() call, called within a WPAR.

As per the current design, the vmgetinfo() call uses a frame work to get the statistics when called from the global LPAR, as it is costly to maintain the same kind of frame work for each WPAR existing in the system, the same kind of frame work is not available inside a WPAR. So vmgetinfo() call has to compute the memory statistics by traversing through all the segment control blocks within a WPAR. Where as in global, there is no need to
traverse through all the segment control blocks, hence vmgetinfo() called from a global has better response time than the one called from a WPAR. This is a trade off as per the current design.

Idea priority Urgent
  • Guest
    Reply
    |     Apr 8, 2020

    IBM has evaluated the priority of this enhancement proposal relative to other future product content and determined that this RFE will not be pursued for a future product release.

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.