OVS Version 2.9.90
DPDK Version 17.11
Ubuntu 17.10 Kernel 4.13.0-21-generic
Docker 18.06.1-ce
I figured out that no hugepage was being consumed by any of the
switches. What is happening is that when ovs-vswitchd is starting, the
number of free hugepages drop all the way to 0 (in /dev/hugepages, I
Thanks for the response all.
@Ian
1GB pagesize, 8 total pages. OVS is launched without the
dpdk-socket-mem options so it should take 1GB. When one switch is
started, free hugepage count drops to 7. When I launch another, I'd
expect it to drop to 6 but it crashes instead.
My DPDK apps create the
> On Thu, Oct 25, 2018 at 09:51:38PM +0200, Alan Kayahan wrote:
> > Hello,
> >
> > I have 3 OVS bridges on the same host, connected to each other as
> > br1<->br2<->br3. br1 and br3 are connected to the docker container cA
> > via dpdkvhostuser port type (I know it is deprecated, the app works
> >
On Thu, Oct 25, 2018 at 09:51:38PM +0200, Alan Kayahan wrote:
> Hello,
>
> I have 3 OVS bridges on the same host, connected to each other as
> br1<->br2<->br3. br1 and br3 are connected to the docker container cA
> via dpdkvhostuser port type (I know it is deprecated, the app works
> this way
Hello,
I have 3 OVS bridges on the same host, connected to each other as
br1<->br2<->br3. br1 and br3 are connected to the docker container cA
via dpdkvhostuser port type (I know it is deprecated, the app works
this way only). The DPDK app running in cA generate packets, which
traverse bridges
