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

datapath concurrency map access #69

Open
abhi opened this issue Nov 16, 2016 · 1 comment
Open

datapath concurrency map access #69

abhi opened this issue Nov 16, 2016 · 1 comment

Comments

@abhi
Copy link
Member

abhi commented Nov 16, 2016

No description provided.

@unclejack
Copy link
Contributor

@abhinandanpb: Is this done?

wenyingd pushed a commit to wenyingd/ofnet that referenced this issue Aug 23, 2023
Instead of 128.
65535 means that there is no buffering and that the full packet is sent
to the controller. This is actually the only value supported by OVS,
even though OVS will not reject other values. This can create confusion
as the flows will show `max_len=128`, but the controller will always
receive the full packet.
Another value for max_len can be explicitly provided using the new
`MaxLen` field in the `NXController` struct, but there should be no
reason to do so when using OVS.

See openvswitch/ovs-issues#295

Signed-off-by: Antonin Bas <[email protected]>
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