Re: [Ryu-devel] Reassemble FlowStatsReply in MULTIPART_REPLY message

: IWAMOTO Toshihiro Sent: Tuesday, 21 August 2018 3:29 PM To: Le Quoc Khanh Cc: IWAMOTO Toshihiro; ryu-devel@lists.sourceforge.net Subject: Re: [Ryu-devel] Reassemble FlowStatsReply in MULTIPART_REPLY message On Thu, 16 Aug 2018 12:23:30 +0900, Le Quoc Khanh wrote: > > [1 ] > Hi IWAMOTO, &

Re: [Ryu-devel] Reassemble FlowStatsReply in MULTIPART_REPLY message

On Thu, 16 Aug 2018 12:23:30 +0900, Le Quoc Khanh wrote: > > [1 ] > Hi IWAMOTO, > > Thank you for your answer but I still do not really get how the replies are > accumulated. I could not figure out where in the *'ryu.app.ofctl_rest.py > '* the *self.waiters* was fir

Re: [Ryu-devel] Reassemble FlowStatsReply in MULTIPART_REPLY message

Hi IWAMOTO, Thank you for your answer but I still do not really get how the replies are accumulated. I could not figure out where in the *'ryu.app.ofctl_rest.py '* the *self.waiters* was first created for each MULTIPART_REPLY message that is divided into multiple mess

Re: [Ryu-devel] Reassemble FlowStatsReply in MULTIPART_REPLY message

On Tue, 14 Aug 2018 08:08:03 +0900, wrote: > > [1 ] > [1.1 ] > Hi all, > > I am developing a flow monitoring app using FlowStatsRequest/Reply. However, > when the number of flows on switch exceed 682, the switch start breaking the > data into MULTIPART_REPLY message and send back to the cont

[Ryu-devel] Reassemble FlowStatsReply in MULTIPART_REPLY message

Hi all, I am developing a flow monitoring app using FlowStatsRequest/Reply. However, when the number of flows on switch exceed 682, the switch start breaking the data into MULTIPART_REPLY message and send back to the controller as a sequence of FlowStatsReply with the same msg.xid and the OFPMP