Re: [ovs-dev] [Single DP 08/15] Separate OpenFlow port numbers from datapath ones.

2012-10-30 Thread Ben Pfaff
On Tue, Oct 30, 2012 at 03:34:32PM -0700, Justin Pettit wrote: > On Oct 22, 2012, at 3:11 PM, Ben Pfaff wrote: > > We want to avoid quickly reusing OpenFlow port numbers. Previously, > > that was indirectly implemented through dpif-linux, which makes an > > effort to avoid quickly reusing kernel

Re: [ovs-dev] [Single DP 08/15] Separate OpenFlow port numbers from datapath ones.

2012-10-30 Thread Justin Pettit
On Oct 22, 2012, at 3:11 PM, Ben Pfaff wrote: > "git am" says: > >Applying: Separate OpenFlow port numbers from datapath ones. >/home/blp/ovs/.git/rebase-apply/patch:230: trailing whitespace. > >warning: 1 line adds whitespace errors. >Press any key to continue… Whoops. > In t

Re: [ovs-dev] [Single DP 08/15] Separate OpenFlow port numbers from datapath ones.

2012-10-22 Thread Ben Pfaff
On Thu, Oct 18, 2012 at 12:51:53PM -0700, Justin Pettit wrote: > In a future commit, we will make multiple bridges share a single backing > datapath. Our simple mapping from datapath to OpenFlow port numbers > won't work, since we'll want the same OpenFlow port numbers on different > bridges. For

[ovs-dev] [Single DP 08/15] Separate OpenFlow port numbers from datapath ones.

2012-10-18 Thread Justin Pettit
In a future commit, we will make multiple bridges share a single backing datapath. Our simple mapping from datapath to OpenFlow port numbers won't work, since we'll want the same OpenFlow port numbers on different bridges. For example, the OFPP_LOCAL port must be the same on all bridges, but will