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

Different packet size spaces #6

Open
h33p opened this issue Dec 5, 2023 · 0 comments
Open

Different packet size spaces #6

h33p opened this issue Dec 5, 2023 · 0 comments

Comments

@h33p
Copy link
Member

h33p commented Dec 5, 2023

We do have support for different address spaces, but, we do not have support for different sizing - everything is forced to u64. Having different sizing would be crucial for passing arbitrarily large sparse packets for processing. For instance, in memflow we have support for u128 address spaces. Something like that would be desirable here too.

I attempted to give this a stab, however, the problem appears to be rather difficult to solve with all the abstraction layers we have. We may need to bind a T: PacketIo to an additional supertrait that has an associated type for the packet size space. However, there is more research work to be done.

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

1 participant