[dpdk-dev] [RFC v1 0/3] show the Rx/Tx burst description field
haiyue.wang at intel.com
Mon Aug 12 17:39:40 CEST 2019
> -----Original Message-----
> From: David Marchand [mailto:david.marchand at redhat.com]
> Sent: Monday, August 12, 2019 22:27
> To: Wang, Haiyue <haiyue.wang at intel.com>
> Cc: dev <dev at dpdk.org>
> Subject: Re: [dpdk-dev] [RFC v1 0/3] show the Rx/Tx burst description field
> On Mon, Aug 12, 2019 at 4:20 PM Haiyue Wang <haiyue.wang at intel.com> wrote:
> > Since some PMDs have multi-path for Rx/Tx, FD.io VPP will tell you in
> > the Debug CLI what rx/tx function is being used:
> > #show hardware-interface
> > tx burst function: ice_xmit_pkts
> > rx burst function: ice_recv_scattered_pkts
> > But if the tx/rx is static, then 'dladdr' will return nil:
> > tx burst function: (nil) │······················
> > rx burst function: (nil) │······················
> > For making things consistent and gracefull, we introduce an new string
> > field to describe the Rx/Tx burst information. This is vendor-neutral,
> > it is used to identify the Rx/Tx burst selection if the PMD has more
> > than one.
> > If a PMD supports this, then rxqinfo/txqinfo->burst_info != '\0'.
> The rx/tx handlers are the same for all queues of a ethdev port.
> What is the added value to put this in a per queue api ?
We will add support Receive Flex Descriptor per queue in 19.11:
drivers/net/ice/base/ice_lan_tx_rx.h --> enum ice_rxdid
Then the burst_info will be Vector (generic info) + RXDID info,
that's why we changed the design from const char * to char .
> David Marchand
More information about the dev