On Tue, Oct 30, 2012 at 05:37:07PM -0700, Justin Pettit wrote: > > On Oct 22, 2012, at 3:54 PM, Ben Pfaff <b...@nicira.com> wrote: > > > On Thu, Oct 18, 2012 at 12:51:55PM -0700, Justin Pettit wrote: > >> These commands will be useful in a future commit that makes multiple > >> bridges share a single backing datapath. The ovs-dpctl commands will > >> show information about the backing datapath, so it will be difficult to > >> determine which information belongs to which bridge. The new "dpif/*" > >> ovs-appctl commands return information about the bridge--regardless of > >> how the backing datapath is configured. > >> > >> Signed-off-by: Justin Pettit <jpet...@nicira.com> > > > > Users are already confused enough (and rightly so) about the > > difference between "ovs-ofctl dump-flows" and "ovs-dpctl dump-flows" > > (and other uses of these programs). Adding a third way is going to > > make their heads spin. I suggest adding some explanation to the > > manpage text for each program/fragment, and perhaps a FAQ entry giving > > an overview. > > Don't forget "ovs-appctl bridge/dump-flows". :-) > > I added a reference to "ovs-ofctl dump-flows" in the "ovs-dpctl > dump-flows" and "ovs-appctl dpif/dump-flows", since that's what people > usually want to see. Unless you object, I'll add a FAQ entry in the > final patch, since that makes this new dump-flows actually useful, and > we'd need to rewrite then, anyway.
Sounds great. Thank you! _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
