Thanks Deniele,
I can't see any design note in your repo
(https://github.com/ddiproietto/ovs/tree/userconntrack_20151115) regarding
conntrack in userspace.
I have already gone through -
1. conntrack related presentations given during fall conference
2. code walkthrough in your repo for
Andy Zhou wrote on 02/08/2016 01:54:06 PM:
> From: Andy Zhou
> To: Ryan Moats/Omaha/IBM@IBMUS
> Cc: discuss@openvswitch.org
> Date: 02/08/2016 01:54 PM
> Subject: Re: [ovs-discuss] Some more scaling test results...
>
> On Fri, Feb 5, 2016 at 5:26 PM, Ryan Moats wrote:
> Today, I stood up a fi
On Fri, Feb 5, 2016 at 5:26 PM, Ryan Moats wrote:
> Today, I stood up a five node openstack cloud on machines with 56 cores
> and 256GB of memory and ran a scaling test to see if I could
> stamp out 8000 copies of the following pattern in a single project
> (tenant): n1 --- r1 --- n2 (in other wo
Thanks Joe for your reply. Its build now after giving the linux path.
May I know the connection tracking commands? We can see packets are going
to connection tracking functions but haven't found any command to check the
tracked packets info or table.
This will be helpful if you can send tracking
Quoting Ansis Atteka (ansisatt...@gmail.com):
> On 2 February 2016 at 23:33, Serge Hallyn wrote:
>
> > Quoting Ansis Atteka (ansisatt...@gmail.com):
> > > On 29 January 2016 at 12:10, Serge Hallyn
> > wrote:
> > > > Sorry I've not really had anything to add here, I'm just not familiar
> > > > en
>
> I am hypothesizing that perhaps the *patch* port is just a configuration
> construct to tell the OVS kernel module that the ports on two OVS bridges
> are connected. Then, somehow the kernel module is able to forward the
> packets between the two bridges more efficiently than over a *veth* pair
