Light

meshsr / onetswitch30 Goto Github PK

View Code? Open in Web Editor NEW

7.0 6.0 11.0 31.88 MB

Reference Designs for ONetSwitch30

License: GNU Lesser General Public License v2.1

Tcl 20.22% Verilog 79.32% Shell 0.46%

onetswitch30's Introduction

###onetswitch30 This repo stores all Getting-Started projects and reference designs for ONetSwitch30.

All the documents are provided in MeshSr Wiki.
Please visit our wiki pages for more information.

onetswitch30's People

Contributors

Stargazers

Watchers

Forkers

zingszhang lc641777437 lparkes missmhwgo torvalds2010 wanming2008 chengchenhu harlequin-tech kangjian888 paramvahtech

onetswitch30's Issues

Segmentation fault by using dpctl stats-flow in ofs-hw

Hi,

I'm evaluating the ONetSwitch running the OpenFlow switch with hardware tables. (ons30-app52-ref_ofshw)

When I run the switch with some installed flows I can not use dpctl to get the flow statistics (stats-flow command). I will get a segmentation fault:

~/ofs-hw/utilities # ./dpctl tcp:127.0.0.1:6632 stats-flow

SENDING:
stat_req{type="flow", flags="0x0", table="all", oport="any", ogrp="any", cookie=0x0", mask=0x0", match=oxm{all match}}

Segmentation fault

My system information:

~/ofs-hw/utilities # uname -a
Linux (none) 3.12.0-xilinx-dirty #2 SMP PREEMPT Tue Oct 13 20:42:30 CST 2015 armv7l GNU/Linux
~/ofs-hw/utilities # cd ..
~/ofs-hw # ./udatapath/ofdatapath --version

This is ONetSwitch30, with hardware version: v1.3, tables: 3, size: 16
ofdatapath 1.3.0 compiled Jun 29 2015 15:53:55
~/ofs-hw # ./secchan/ofprotocol --version
ofprotocol 1.3.0 compiled May 19 2015 13:41:00
~/ofs-hw # ./utilities/dpctl --version
dpctl 1.3.0 compiled Jun 19 2015 16:45:14

If I use the dpctl tool from the ofs-sw folder, the stats-flow command works fine:

~/ofs-sw/utilities # ./dpctl tcp:127.0.0.1:6632 stats-flow

SENDING:
stat_req{type="flow", flags="0x0", table="all", oport="any", ogrp="any", cookie=0x0", mask=0x0", match=oxm{all match}}


RECEIVED:
stat_repl{type="flow", flags="0x0", stats=[{table="0", match="oxm{in_port="1"}", dur_s="1567", dur_ns="361000", prio="1", idle_to="0", hard_to="0", cookie="0x0", pkt_cnt="0", byte_cnt="0", insts=[apply{acts=[out{port="2"}]}]}, {table="0", match="oxm{in_port="2"}", dur_s="1300", dur_ns="61000", prio="1", idle_to="0", hard_to="0", cookie="0x0", pkt_cnt="0", byte_cnt="0", insts=[apply{acts=[out{port="1"}]}]}, {table="0", match="oxm{in_port="4"}", dur_s="1008", dur_ns="230000", prio="1", idle_to="0", hard_to="0", cookie="0x0", pkt_cnt="0", byte_cnt="0", insts=[apply{acts=[out{port="2"}]}]}, {table="1", match="oxm{in_port="3"}", dur_s="1219", dur_ns="527000", prio="1", idle_to="0", hard_to="0", cookie="0x0", pkt_cnt="0", byte_cnt="0", insts=[apply{acts=[out{port="1"}]}]}, {table="1", match="oxm{in_port="4"}", dur_s="1029", dur_ns="249000", prio="1", idle_to="0", hard_to="0", cookie="0x0", pkt_cnt="0", byte_cnt="0", insts=[apply{acts=[out{port="2"}]}]}, {table="2", match="oxm{in_port="4"}", dur_s="988", dur_ns="265000", prio="1", idle_to="0", hard_to="0", cookie="0x0", pkt_cnt="0", byte_cnt="0", insts=[apply{acts=[out{port="2"}]}]}, {table="3", match="oxm{in_port="4"}", dur_s="967", dur_ns="615000", prio="1", idle_to="0", hard_to="0", cookie="0x0", pkt_cnt="0", byte_cnt="0", insts=[apply{acts=[out{port="2"}]}]}, {table="4", match="oxm{in_port="4"}", dur_s="1135", dur_ns="775000", prio="1", idle_to="0", hard_to="0", cookie="0x0", pkt_cnt="0", byte_cnt="0", insts=[apply{acts=[out{port="2"}]}]}, {table="10", match="oxm{in_port="4"}", dur_s="1092", dur_ns="75000", prio="1", idle_to="0", hard_to="0", cookie="0x0", pkt_cnt="0", byte_cnt="0", insts=[apply{acts=[out{port="2"}]}]}]}

The ofs-sw version of dpctl is:

~/ofs-sw/utilities # ./dpctl --version
dpctl 1.3.0 compiled Dec 17 2014 14:07:04

Can you reproduce this behaviour and do you know what is wrong with the "ofs-hw" version of dpctl?

Thanks!

idle and hard timeout for flows don't work

Hi,
I am trying to program flows with an idle_timeout and hard_timeout in a OneSwitch30 board. But it doesn't work well:

The idle_timeout expires although the flow is used all time, so the OFPFlowRemoved message is generated even though the flow receives traffic. But the flow is not really removed from flow-table, because the messages which match with this flow are forwarding like before the OFPFlowRemoved message generation.
- The hard_timeout expires and a OFPFlowRemove message is generated correctly. But as in idle_timeout case, the flow entry is not removed from flow-table.

Could you help me with any idea?

Best regards.

Recommend Projects

React

A declarative, efficient, and flexible JavaScript library for building user interfaces.
Vue.js

🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript

TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
TensorFlow

An Open Source Machine Learning Framework for Everyone
Django

The Web framework for perfectionists with deadlines.
Laravel

A PHP framework for web artisans
D3

Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

javascript

JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
web

Some thing interesting about web. New door for the world.
server

A server is a program made to process requests and deliver data to clients.
Machine learning

Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Visualization

Some thing interesting about visualization, use data art
Game

Some thing interesting about game, make everyone happy.

Recommend Org

Facebook

We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft

Open source projects and samples from Microsoft.
Google

Google ❤️ Open Source for everyone.
Alibaba

Alibaba Open Source for everyone
D3

Data-Driven Documents codes.
Tencent

China tencent open source team.