Hi Ben, I did not quite understand your reply to the first question. what does the expression "openvswitch_mod.ko does no flow expiration" mean then? Also, you mentioned "userspace deletes flows that fall idle" : you mean vswitchd deletes them from the database? For my use case, what I am doing is configuring all required flows when openvswitch starts up, and i require them to exist whenever necessary unless the vswitchd process actually dies. Is there a way to do this? (I need flows to always exist in vswitchd).
If this is not possible, how do we know when to re-push the flow rules? A side question: Is flow information actually stored in the database, or does the database hold only port/bridge information. I do not see any flow table in the database document description. Thanks, Aish On Wed, Sep 21, 2011 at 12:23 PM, Ben Pfaff <[email protected]> wrote: > On Wed, Sep 21, 2011 at 11:46:36AM -0700, Aishwarya wrote: > > That was very helpful. Thanks! One of the slides say that the kernel > module > > has no flow expiration . I am guessing this means that as it gets to know > > about more and more flows from vswitchd, these will always be there in > the > > kernel as long as it is loaded? > > No. Userspace deletes flows that fall idle for some time. > > > Also, If I have lets say 7000 flows, and send some traffic for each flow, > so > > that the kernel module ultimately knows about all the flows. How fast is > its > > lookup now when it starts receiving packets, lets say of the oldest flow? > > Fast. It's a hash table. >
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
