[dpdk-dev] [PATCH v3 0/5] A means to negotiate delivery of Rx meta data
Thomas Monjalon
thomas at monjalon.net
Fri Oct 1 11:32:45 CEST 2021
01/10/2021 10:54, Andrew Rybchenko:
> >> Thomas, if I'm not mistaken, net/mlx5 dv_xmeta_en driver option
> >> is vendor-specific way to address the same problem.
> >
> > Not exactly, it is configuring the capabilities:
> > +------+-----------+-----------+-------------+-------------+
> > | Mode | ``MARK`` | ``META`` | ``META`` Tx | FDB/Through |
> > +======+===========+===========+=============+=============+
> > | 0 | 24 bits | 32 bits | 32 bits | no |
> > +------+-----------+-----------+-------------+-------------+
> > | 1 | 24 bits | vary 0-32 | 32 bits | yes |
> > +------+-----------+-----------+-------------+-------------+
> > | 2 | vary 0-24 | 32 bits | 32 bits | yes |
> > +------+-----------+-----------+-------------+-------------+
>
> Sorry, but I don't understand the difference. Negotiate is
> exactly about capabilities which we want to use.
The difference is that dv_xmeta_en is not enabling/disabling
the delivery of mark/meta.
It is just extending the scope (cross-domain) and the size.
I think this is not covered in your proposal.
More information about the dev
mailing list