Skip to Main Content
IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage products. 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.

Status Future consideration
Created by Guest
Created on Feb 3, 2025

Command to force Dynamic Pagepool to shrink to minimum size

When utilizing the dynamic pagepool during IO operations, the pagepool automatically expands until possibly reaching its maximum allocated size. It then remains at that level, even after the IO operations have completed, until additional memory (more than is free) is needed by another application. This behavior can create challenges in two key areas:

  1. Node Cleanup: The process of cleaning up nodes becomes more complex as the pagepool does not automatically shrink after reaching its maximum size.
  2. Health Checks: Monitoring and verifying the health of available memory is more difficult since the pagepool remains at its expanded size (or any size between max and min), even when pagepool memory demand is low.

To address these issues, implementing a command that forces the pagepool to shrink back to its minimum size would be beneficial. This functionality would enable the system to return to a default state more efficiently, ensuring smoother operation via easier transitions between users and applications. 

Idea priority High