From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dev-bounces@dpdk.org>
Received: from dpdk.org (dpdk.org [92.243.14.124])
	by inbox.dpdk.org (Postfix) with ESMTP id 3C766A0471
	for <public@inbox.dpdk.org>; Mon, 12 Aug 2019 16:27:26 +0200 (CEST)
Received: from [92.243.14.124] (localhost [127.0.0.1])
	by dpdk.org (Postfix) with ESMTP id D6A5A378B;
	Mon, 12 Aug 2019 16:27:24 +0200 (CEST)
Received: from mail-vs1-f48.google.com (mail-vs1-f48.google.com
 [209.85.217.48]) by dpdk.org (Postfix) with ESMTP id 37CF0326D
 for <dev@dpdk.org>; Mon, 12 Aug 2019 16:27:23 +0200 (CEST)
Received: by mail-vs1-f48.google.com with SMTP id i128so905222vsc.7
 for <dev@dpdk.org>; Mon, 12 Aug 2019 07:27:23 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:cc:content-transfer-encoding;
 bh=NEReB4C/kWFPT+8vLcyxB6NBYQJRKK72MPbJ4mK1JVI=;
 b=e0CFcc/CIekoOOOSXgCY2fophvTdWJpj4iEKVOxcgYwHpW/x/tblDVyX7NuBKaRVJK
 EMMWhwkg08/rhlgUkCyEwAVEjOi3H9HaQjyBAd+vZ+INKM361uVAGNZKqop51bxORQAM
 iDHMjkemqecUit9myT0BPslz9/2PvWiq/NrqBCWdgf0XhO4mUPnMfDtYW+SRJkm0vSyL
 24P1PeSILmJp9e5cLyLqWAi5KvoQyBafTlqV81D5BkrNiDjTsGOldAr/F2nk/gPM430M
 mdSC7G+fBHbCHNR7RJgiVo0Hw4Q+e0CNOByhztNI6k8lwABHfERNYLpp5A5o4Bg9QhkD
 9ukw==
X-Gm-Message-State: APjAAAWLtVx/dcF6K5q0+u/3B0qj3ymkjOZHb0zga6A63njBl3HtRZo+
 lU6dSAkkeuZV1aH6FveHOU+6TomDLzcsyysDhcQIcA==
X-Google-Smtp-Source: APXvYqztc29KOCiPqIP4OWMHAC4VjeuvU477GGRgpxHMXzYEwTB+wAHXlAS/zrhd2672vw1QDCqgeSfYHb1cNP+ZgTA=
X-Received: by 2002:a67:fb58:: with SMTP id e24mr8636543vsr.141.1565620042539; 
 Mon, 12 Aug 2019 07:27:22 -0700 (PDT)
MIME-Version: 1.0
References: <1565619305-17116-1-git-send-email-haiyue.wang@intel.com>
In-Reply-To: <1565619305-17116-1-git-send-email-haiyue.wang@intel.com>
From: David Marchand <david.marchand@redhat.com>
Date: Mon, 12 Aug 2019 16:27:11 +0200
Message-ID: <CAJFAV8zFd5jMAtocx9K-ds6khWkTbS-K1_Qi5jQf4+W1dsOLAQ@mail.gmail.com>
To: Haiyue Wang <haiyue.wang@intel.com>
Cc: dev <dev@dpdk.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [dpdk-dev] [RFC v1 0/3] show the Rx/Tx burst description field
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Mon, Aug 12, 2019 at 4:20 PM Haiyue Wang <haiyue.wang@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) =E2=94=82=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=
=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=
=B7=C2=B7=C2=B7=C2=B7=C2=B7
>          rx burst function: (nil) =E2=94=82=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=
=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=B7=C2=
=B7=C2=B7=C2=B7=C2=B7=C2=B7
>
> 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] !=3D '\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 ?


--=20
David Marchand