Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request Request] SetTensorAddress for plugin's input/outputs #4252

Closed
tp-nan opened this issue Nov 18, 2024 · 1 comment
Closed

[Request Request] SetTensorAddress for plugin's input/outputs #4252

tp-nan opened this issue Nov 18, 2024 · 1 comment

Comments

@tp-nan
Copy link

tp-nan commented Nov 18, 2024

Hi, Is it possible for a plugin to have a SetTensorAddress for the plugin's inputs/outputs? Or to have an IPluginOutputAllocator to manage its input/output addresses? Supporting this feature would be beneficial for users to manage the input/output memory locations of the plugin themselves.

@tp-nan tp-nan changed the title [Request Request] IPluginAllocator or SetTensorAddress for plugin's input/outputs [Request Request] IPluginOutputAllocator or SetTensorAddress for plugin's input/outputs Nov 18, 2024
@tp-nan tp-nan changed the title [Request Request] IPluginOutputAllocator or SetTensorAddress for plugin's input/outputs [Request Request] SetTensorAddress for plugin's input/outputs Nov 18, 2024
@tp-nan tp-nan closed this as completed Nov 19, 2024
@lix19937
Copy link

If plugin is inside of model, the address controled by trt, if plugin is at edge of model, user can control it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants