On Fri, Sep 15, 2017 at 07:00:40PM +0000, Darrell Ball wrote:
> > In this case, we have what seems like a clear distinction b/w Napatech
> which does not need the
> > queue action workaround and everything else, which does.
> > Besides the non-Napatech behavior, which is worrisome, maintaining the
> difference for flow handling
> > under the covers is concerning.
> >
> > I wonder if we should be upfront as possible here and just have a dpdk
> interface configuration – maybe
> > something like “supports native HWOL mark action” since the better
> behavior is the exception?
> > The interface config would be more robust than probing.
> > This would need documentation, of course.
>
> The thing is that the option is fixed, while the NIC driver may change.
> Such option may apply to old versions may not apply to newer versions.
>
> [Darrell] If the limitation is only at driver layer, then that would be good
> and we should identify
> that in discussion with Intel and Mellanox. In the case of a
> ‘good driver version’, the user would consult the
> documentation and use the new driver version if possible and
> configure as
> “supports native HWOL mark action”.
> At least in one case, my understanding was that there was no
> plan to fix this, although that plan may
> change of course.
From what I know, it's unfortunately true.
> Anyways, if you want to support probing in the next patchset,
> then that is fine.
Yes, I will think about it.
> But, I think we still need verbose documentation about the
> nics differences in OVS docs, including the impact
> on receive queue, as used by OVS-DPDK.
No objections.
> > I think anyways we need documentation describing the difference b/w
> nics in the dpdk documentation (howto part).
>
> IIRC, there was already an ask from the DPDK mailing list.
>
> [Darrell] I meant we need to document this in OVS since we have OVS code that
> is exposed to these differences.
Okay, makes sense. I will start a doc and let other venders to fill it.
--yliu
_______________________________________________
dev mailing list
[email protected]
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
