[ovs-dev] [PATCH 12/25] netdev-offload-dpdk: Introduce map APIs for table id and miss context

William Tu u9012063 at gmail.com
Sun Jul 12 16:18:55 UTC 2020


On Sat, Jul 11, 2020 at 11:22 PM Eli Britstein <elibr at mellanox.com> wrote:
>
>
> On 7/11/2020 9:44 PM, William Tu wrote:
> > On Mon, Jan 20, 2020 at 7:09 AM Eli Britstein <elibr at mellanox.com> wrote:
> >> Different vports are differentiated in HW by different tables, as in the
> >> SW model. As such we need to map to table ids. Also, as this offload
> >> involves multiple tables, a miss might occur in the target table. In
> >> such case we need to recover the packet and continue in SW. Introduce a
> >> mapping for a miss context for that.
> >>
> > Hi Eli,
> >
> > Can you elaborate a little more on
> > "Different vports are differentiated in HW by different tables, as in
> > the SW model."?
> >
> > Do you mean for each tunnel type in HW, there is a separate table?
> > ex: a vport such as vxlan_sys_4789 has one table, and gre_sys has another table?
> >
> > And is this table in HW or in SW?
>
> Yes. In SW there is a match on the in_port (vxlan_sys_4789, gre_sys and
> also non-vports). This is equivalent to different logical tables. In HW,
> in this patch-set this is done by different groups (HW different tables).
>
> Please note that we would like to progress with an approach to enhance
> DPDK and put some of the logic inside the PMD. See:
>
> Link to RFC: http://mails.dpdk.org/archives/dev/2020-June/169656.html
> Link to patchset: http://mails.dpdk.org/archives/dev/2020-June/171590.html

Thank you!
I will check it out.
William


More information about the dev mailing list