On Thu, 18 Apr 2019 at 14:00, Aaron Conole wrote:
>
> Ansis Atteka writes:
>
> > On Wed, 17 Apr 2019 at 13:07, Aaron Conole wrote:
> >>
> >> These are used for interfacing with conntrack, as well as by some
> >> DPDK PMDs
> >
> > Did you get these with audit2allow? If so, then looks good to me.
21/04/2019 11:11, Ophir Munk:
> Thomas - would you like to explain more on the origins of "rte"?
Ian explained (below) the origin quite clearly.
It has been decided in the early days by Intel.
> From: Ian Stokes
> > On 4/17/2019 5:34 PM, Ben Pfaff wrote:
> > > On Wed, Apr 17, 2019 at 11:45:33AM
Hello,
Would you be interested in quoting for an upcoming project at my property.
Please let know me if you would be able to pop in and book me in your schedule
so I can make myself available to have an appointment with you.
Many thanks
___
dev
Thomas - would you like to explain more on the origins of "rte"?
Please note that dpdk API and its public data structures use an rte_ prefix,
for example:
rte_create_flow(). This is a convenient way to know when we are directly
calling/accessing the DPDK library.
In parallel we should avoid
From: Roni Bar Yanai
vport offloaded functions should have a different implementation for
kernel based OVS versus dpdk based OVS. Currently there is an unconditional
execution of a kernel based calls even if the vport was added by dpif-netdev
rather than by dpif-netlink. Before this commit and
