To clarify:
For the behavior you propose to work, send() on a Datapath would have to return
True or False - so as to communicate to the application that called send() that
the particular call to send() succeeded or failed.
A failed send() (returning False) would indicate to the application that
Ah; OK.
So, since we were trying to close file descriptors properly, there's one of two
ways to accomplish that:
1) Have an echo request loop that does it automatically (and we now have
available, but not enabled by default).
2) Have the application call close() on a Datapath that it considers "
On Wed, 2 Mar 2016 04:09:46 +
Victor Orlikowski wrote:
> How would the core know when an application's record of a Datapath object is
> stale?
>
> I modeled these changes, to a certain degree, after what the dpset and
> topology applications do; none of these samples use either of those, s
No problem!
I've got some more *minor* cleanups upcoming (removing the close_requested
variable, and similar) - but that needs testing first, before I submit it.
None of what I plan to submit, however, should significantly change
functionality (or anything user exposed).
Best,
Victor
--
Victor
So...
How would the core know when an application's record of a Datapath object is
stale?
I modeled these changes, to a certain degree, after what the dpset and topology
applications do; none of these samples use either of those, so I did the
simplest thing possible to do something similar, as
Can Ryu core instead of an applications close the connection of a dead
datapath?
On Fri, 26 Feb 2016 17:42:33 + Victor Orlikowski
wrote:
> Update applications to remember and close() old Datapaths that may not longer
> be valid.
>
> Signed-off-by: Victor J. Orlikowski
>
> ---
> ryu/app/
On Tue, 1 Mar 2016 11:30:26 +0900
FUJITA Tomonori wrote:
> 2016-03-01 11:24 GMT+09:00 IWAMOTO Toshihiro :
>> At Fri, 26 Feb 2016 17:29:43 +,
>> Victor Orlikowski wrote:
>>>
>>> Protect events queue with a semaphore, due to a discovered bug in eventlet
>>> queue put(). This is a temporary wor
I fixed this issue.
In fact I have to use the -O option to specify the openflow version
ovs-ofctl dump-flows mybridge
*-O OpenFlow13*
Thanks.
2016-03-01 2:09 GMT-08:00 David Gabriel :
> Dears
>
> Thanks Shinpei for your help.
> I have fixed my issue but when I use this command 'ovs-ofctl dump-fl
Dears
Thanks Shinpei for your help.
I have fixed my issue but when I use this command 'ovs-ofctl dump-flows
mybridge' to get the flows deails it shows me this kind of error after
displaying few flows. Please note that when I disable writing metadata the
content is well displayed.
ovs-ofctl dump-f
