Sorry for the delay,

On Tue, 1 Oct 2013 14:18:29 -0400
Chen Chen <[email protected]> wrote:

> *@handler.set_ev_cls(dpset.EventDP, dpset.DPSET_EV_DISPATCHER)*
> *def switch_connection_handler(self, event):*
> *        datapath = event.dp*
> *        datapath.send_msg(datapath.ofproto_parser.OFPSetConfig(*
> *                                     datapath,*
> *                                     datapath.ofproto.OFPC_FRAG_NORMAL,*
> *                                     256))*
> *
> *
> And then I tried to use CONFIG_REQUEST message to retrieve the
> miss_send_len value of the switch:
> *
> *
> *datapath.send_msg(datapath.ofproto_parser.OFPGetConfigRequest(datapath))*
>  *
> *
> On the other hand, I wrote an event handler to process the CONFIG_REPLY
> message:
> 
> *@handler.set_ev_cls(ofp_event.EventOFPGetConfigReply, handler.MAIN_DISPATCH
> **ER)*
> *    def get_config_reply_handler(self, ev):*
> *        msg = ev.msg*
> * datapath = msg.datapath*
> *        print "switch: %s's miss_send_len is:%d" % (dpid_to_str(datapath.id),
> m**sg.miss_send_len)*
> *
> *
> When running the code, I get the following result:
> 
> *switch: 00001afe86e1a141's miss_send_len is:256*
> *
> *
> But when I checked the configuration in ovs, I still got miss_send_len=0:
> 
> OFPT_FEATURES_REPLY (xid=0x2): dpid:00001afe86e1a141
> n_tables:254, n_buffers:256
> ...
> OFPT_GET_CONFIG_REPLY (xid=0x4): frags=normal *miss_send_len=0*
> 
> So there is some inconsistent feedback from ryu and ovs. And I still have
> empty-packet_in problem.
> Any advice on this issue? Thank you.

>From quick look at OVS code, ovs-octl always gives zero
miss_send_len. I have no clue why you get zero data in packet_in. By
default, no zero value is set to miss_send_len. How you configure OVS?

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60134071&iu=/4140/ostg.clktrk
_______________________________________________
Ryu-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ryu-devel

Reply via email to