On Sun, Jan 15, 2017 at 06:14:47PM +, Stokes, Ian wrote:
> > Since it's possible to delete memory pool in DPDK we can try to estimate
> > better required memory size when port is reconfigured, e.g. with different
> > number of rx queues.
>
> Thanks for the patch.
>
> It will need to be rebase
> Since it's possible to delete memory pool in DPDK we can try to estimate
> better required memory size when port is reconfigured, e.g. with different
> number of rx queues.
Thanks for the patch.
It will need to be rebased for it to apply cleanly to master.
I've applied the changes manually just
On Wed, Nov 09, 2016 at 08:02:49AM -0500, Robert Wojciechowicz wrote:
>
> Hi,
>
> I started working on this patch after this discussion:
> https://mail.openvswitch.org/pipermail/ovs-discuss/2016-September/042643.html
>
> It turned out that it is not possible in OVS to allocate 64 rx queues
> for
Hi,
I started working on this patch after this discussion:
https://mail.openvswitch.org/pipermail/ovs-discuss/2016-September/042643.html
It turned out that it is not possible in OVS to allocate 64 rx queues
for two ports, so I started wondering if we can allocate this memory
dynamically instead
Since it's possible to delete memory pool in DPDK
we can try to estimate better required memory size
when port is reconfigured, e.g. with different number
of rx queues.
Signed-off-by: Robert Wojciechowicz
---
lib/netdev-dpdk.c | 85 +++
1 file
