Skip to content

RDKBDEV-3353: RDKCOM-5506 IPQ: Increase host object size for IPQ devices#32

Open
VedhaLoganathan wants to merge 1 commit into
rdkcentral:developfrom
VedhaLoganathan:ipq_upstream3
Open

RDKBDEV-3353: RDKCOM-5506 IPQ: Increase host object size for IPQ devices#32
VedhaLoganathan wants to merge 1 commit into
rdkcentral:developfrom
VedhaLoganathan:ipq_upstream3

Conversation

@VedhaLoganathan
Copy link
Copy Markdown

IPQ: Increase host object size for IPQ devices

IPQ platforms support a higher number of clients compared. The existing host object size was insufficient to handle this increased client load. This change increases the host object size to ensure proper handling and avoid resource limitations.

Reason:

  • IPQ supports more clients, requiring larger host object allocation.

@VedhaLoganathan VedhaLoganathan requested review from a team as code owners December 15, 2025 08:59
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Dec 15, 2025

All contributors have signed the CLA ✍️ ✅
Posted by the CLA Assistant Lite bot.

@pradeeptakdas pradeeptakdas changed the title IPQ: Increase host object size for IPQ devices RDKBDEV-3353: RDKCOM-5506 IPQ: Increase host object size for IPQ devices Jan 28, 2026
Copy link
Copy Markdown

@tinaelizabeth84 tinaelizabeth84 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Comment from Component owner:
How much memory increase in LMLite component with this change? By default do you see it increase? and does memory usage increase when you have 512 entries in the host table? If its not much, we can make this a generic change
@VedhaLoganathan please address this comment

@tinaelizabeth84
Copy link
Copy Markdown

@VedhaLoganathan please fix the merge conflict and review comments from component owner

@AkhilaReddyK7 AkhilaReddyK7 added the community-contribution Contribution from community label Mar 17, 2026
@AkhilaReddyK7
Copy link
Copy Markdown

@VedhaLoganathan
Can you please fix the review comments and rebase the PR

@VedhaLoganathan
Copy link
Copy Markdown
Author

Comment from Component owner: How much memory increase in LMLite component with this change? By default do you see it increase? and does memory usage increase when you have 512 entries in the host table? If its not much, we can make this a generic change @VedhaLoganathan please address this comment

Memory impact is minimal. The change increases the limit from 200 to 512, but memory is allocated dynamically in 20-entry steps. Maximum increase is ~180 KB (only when 512 devices are connected). With typical deployments, memory usage is identical. The original 200-device limit was set in RDKB-23038. Before making this generic, please verify if other platforms have constraints from that ticket. If not, the overhead is negligible and this can benefit all platforms.

Signed-off-by: Vedhavalli Loganathan <vedhaval@qti.qualcomm.com>
@VedhaLoganathan
Copy link
Copy Markdown
Author

I've already shared the memory usage details in my previous comment. Please let me know if any additional information is needed.

@tinaelizabeth84
Copy link
Copy Markdown

@VedhaLoganathan
I had added this in the RDKBDEV ticket sometime before. Just adding it here too incase you missed to see it
Component owner has raised a concern here on the changes. Please check this at your side. The limit for host table at 200 was intentional.wild card query was failing if we increase the size. Have you checked with 500 Host entries whether wild card query works? It might fail.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

community-contribution Contribution from community

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants