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

the ability to optionally associate packet to tx queue #154

Open
sbuzzard opened this issue May 3, 2022 · 1 comment
Open

the ability to optionally associate packet to tx queue #154

sbuzzard opened this issue May 3, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@sbuzzard
Copy link

sbuzzard commented May 3, 2022

right now for an app, you may be processing packets for a great many logical streams where for each stream it needs to output to the same tx queue to preserve order but to scale would want to spread out the streams across queues. This isn’t currently possible in capsule. Not sure the best api for this.

@sbuzzard sbuzzard added the enhancement New feature or request label May 3, 2022
@sbuzzard
Copy link
Author

note that I am doing this in [my fork[(https://github.com/sbuzzard/capsule/blob/ruby/core/src/runtime/port.rs#L38) but without a general purpose API. I just modified it for my immediate needs: the outbox is a collection of outboxes, each tied to a specific tx-lcore, allowing me to look up the outbox for a given lcore. It doesn't retain the ability to configure a general purposes round robining of transmitted packets to tx lcores, which you'd obviously want to maintain.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Development

No branches or pull requests

1 participant