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.

Sign up for GitHub

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

Jump to bottom

Pipeline values #35

Open
hkwi opened this issue Jun 30, 2016 · 0 comments
Open

Pipeline values #35

hkwi opened this issue Jun 30, 2016 · 0 comments

Comments

@hkwi
Copy link
Contributor

hkwi commented Jun 30, 2016 •
edited
Loading

I want to discuss about the design direction.

While a packet is processed in openflow pipeline, there are some metadata with that packet.

  1. Pipeline fields
    • OXM_OF_IN_PORT
    • OXM_OF_IN_PHY_PORT
    • OXM_OF_METADATA
    • OXM_OF_TUNNEL_ID
  2. Pipeline data
    • "Action Set", which will be updated by OFPIT_WRITE_ACTIONS and OFPIT_CLEAR_ACTIONS
  3. Packet parsing cache information, such as offset to non-vlan header.

At this point of 7c6c713 , we use struct packet_fields for cache information.

How do we implement pipeline fields and pipeline data?
pzanna added a commit that referenced this issue May 28, 2017
@pzanna
Merge pull request #35 from pzanna/Dev_81_Stacking
0692a64 
Dev 81 stacking
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hkwi