From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jagsnn@gmail.com>
Received: from mail-wm1-f54.google.com (mail-wm1-f54.google.com
 [209.85.128.54]) by dpdk.org (Postfix) with ESMTP id C6E2E231E
 for <dev@dpdk.org>; Wed, 20 Feb 2019 12:04:54 +0100 (CET)
Received: by mail-wm1-f54.google.com with SMTP id y185so4436756wmd.1
 for <dev@dpdk.org>; Wed, 20 Feb 2019 03:04:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;
 h=mime-version:from:date:message-id:subject:to;
 bh=ou5U+z9aqM+06pemG0TSStXnxAi5e01DS/CKCzzGObM=;
 b=N9JU1DhpCXlJcGE7sFxpIXkVyF+r6D4rrpVbtut4S7L6c99PN8KaDzKmGC7NfzEVkY
 6mn16j/BsuIEqiCg9KpoHLtf70D2mmdOGsPG+Rm1lmKeImQeLEqjcHfFBXp8hC3oNOGu
 Ghw3fngGXT+LNU+KRfd641XvIBxXXE+bIoF//k7MIkxHLggw/dL0DFEZYOrC/dlw32s9
 o4x+qt8/ZWLv6LmsbMelAbYhc5QGqZq3jkozeIZiEvBV/UubuB+4qEFFw66IPJZ5EjYL
 3NBBFnTRG+irF9+ZhdCQnvCThvHVChBGUwzUVa04zTxxF4xhjfrlaFUWAPWoHhEfo1Wj
 fOjA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20161025;
 h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
 bh=ou5U+z9aqM+06pemG0TSStXnxAi5e01DS/CKCzzGObM=;
 b=RD3YGn3kLtILdbHu3kOy8VpdaQNfeTZ1QecHlcplJxzZs6I1kwsv09XOXKzCQp7fUu
 YR+R9iwAGCGpavMl43XsdI1dsu2kTCPeGSPgAtZCKaQMM5IH8Qtyp18YFEre4QQQv5YO
 8EBGqCGEqpof4qpOIbs1VVQB3KG222eNv0xv3Xvk6CV0JlaLgRzAB4+C34Hei9iYj8FO
 t3BN/DmEzv0KEsasNg+1tYDvdM8UekWoScrShfMPekNnPm77w+xqUz2XwE/HzK/+fnLG
 I2TrKKQ1rI7yMvSSXmiaEciJSXAQXHRTKgVKz0eBT2/CHgxT29qHNsxIdEesH1nDFu2C
 c5xQ==
X-Gm-Message-State: AHQUAubAh2zZcyohHmlD7dXZE/xgPjo7uULWrVjqL60rmo6Fp0jVZKDK
 1nH0s//7R5GS42q9FoIDx1GchvMGbswLXn0It392DaAk
X-Google-Smtp-Source: AHgI3IZJEk2zh5Cbzi/4kt0L7rxi5C0x2EZQoDOoaDtp5y/YkOhXo1v1DR0FkGvnruHsewkjjDTn9XtPOnlcuyAyqbs=
X-Received: by 2002:a1c:a185:: with SMTP id k127mr6169367wme.134.1550660694055; 
 Wed, 20 Feb 2019 03:04:54 -0800 (PST)
MIME-Version: 1.0
From: Jags N <jagsnn@gmail.com>
Date: Wed, 20 Feb 2019 16:34:42 +0530
Message-ID: <CALQkTo0n2NQXwq2PXiB7jQsNY_O+dNypW0WXGvz+_T+Y9eFqUQ@mail.gmail.com>
To: dev@dpdk.org
X-Mailman-Approved-At: Thu, 21 Feb 2019 08:57:45 +0100
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: [dpdk-dev] rte_eth_rx_queue_count support in DPDK FM10k driver.
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>
X-List-Received-Date: Wed, 20 Feb 2019 11:04:54 -0000

Hi,

I am running a DPDK application on host processor. The application is bind
to PCIe Host Interface of an FM10k switch. To prevent FM10k switch from
sending more packets than what the DPDK application can process, the idea
is to have DPDK application check the Rx Queue build up and send pause
frames towards FM10k over the PCIe Host Interface.

To check Rx Queue build up, following DPDK API was looked at, and their
availability for the purpose is mentioned below
i. rte_eth_rx_queue_count   =3D=3D>  returns unsupported by all of the DPDK
version=E2=80=99s FM10k driver.

The question I have is

1) Since "rte_eth_rx_queue_count" is not supported, is there a different
API that would help me find the Rx Queue build up ?
2) What would be the way to get DPDK's FM10k driver implement the
"rte_eth_rx_queue_count" ? Is there someone I could request to help with
the implementation ?
3) Is there any known technical reason for not having the
"rte_eth_rx_queue_count" implemented in DPDK's FM10k driver ? Trying to
understand if there would be anything that would block the implementation
of the API in DPDK FM10k driver.

Regards,
Jags