From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 3A1E0A0A05; Tue, 19 Jan 2021 12:29:11 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id D4083140D06; Tue, 19 Jan 2021 12:29:10 +0100 (CET) Received: from shelob.oktetlabs.ru (shelob.oktetlabs.ru [91.220.146.113]) by mails.dpdk.org (Postfix) with ESMTP id BCEB9140D05 for ; Tue, 19 Jan 2021 12:29:08 +0100 (CET) Received: from [192.168.38.17] (aros.oktetlabs.ru [192.168.38.17]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by shelob.oktetlabs.ru (Postfix) with ESMTPSA id 582E47F4DA; Tue, 19 Jan 2021 14:29:08 +0300 (MSK) DKIM-Filter: OpenDKIM Filter v2.11.0 shelob.oktetlabs.ru 582E47F4DA DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=oktetlabs.ru; s=default; t=1611055748; bh=QY1MRnpT4RzKgxu9yHae8B1aFzjfoacWmde5Y37iiTM=; h=Subject:To:Cc:References:From:Date:In-Reply-To; b=LL/LIRd/4Eot12WUNl7cCdjysjviVRHn1FiZ9xPgmcFw8rmO+SMMTKtKZGsHGMY95 kyKzSag8T4zcdSRm9uHju/fet53k+3fy+ZKwBe7jL5FaX8r9N8/B6WUqyADc45S9jG oz/xWWV20g1XaTvFsPb228zjTtxcNH+mhU44+CC0= To: "Xueming(Steven) Li" Cc: "dev@dpdk.org" , Slava Ovsiienko , Asaf Penso , NBU-Contact-Thomas Monjalon , Ferruh Yigit References: <1611040501-11666-1-git-send-email-xuemingl@nvidia.com> <1611040501-11666-8-git-send-email-xuemingl@nvidia.com> <8edbba36-ab2f-f07a-0133-246afe36d0a3@oktetlabs.ru> From: Andrew Rybchenko Organization: OKTET Labs Message-ID: <3ca21e51-6e1f-9498-69e3-fd8e59f64a02@oktetlabs.ru> Date: Tue, 19 Jan 2021 14:29:08 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v5 8/9] ethdev: add capability of sub-function representor X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 1/19/21 2:19 PM, Xueming(Steven) Li wrote: > >> -----Original Message----- >> From: Andrew Rybchenko >> Sent: Tuesday, January 19, 2021 4:06 PM >> To: Xueming(Steven) Li >> Cc: dev@dpdk.org; Slava Ovsiienko ; Asaf Penso >> ; NBU-Contact-Thomas Monjalon >> ; Ferruh Yigit >> Subject: Re: [PATCH v5 8/9] ethdev: add capability of sub-function representor >> >> On 1/19/21 10:15 AM, Xueming Li wrote: >>> Old DPDK version or some drivers didn't support SubFunction representor. >>> For application to adapt different DPDK version automatically, or to >>> be used for different NICs, this patch introduces new eth device >>> capability of supporting SubFunction representor device. >> >> Sorry, it does not sound sufficient motivation to introduce the capability. I >> simply need real life example why application need to know it. > > I had same internal discussion on this as well :) > A simple example, for customer running DPDK based app with NICs from different vendors, > app need a flag to know whether the device support SF representor, hotplug SF if the > capability shows "support". This also happens with different model/fw even from same vendor. > PMD report device+driver capability that whether SF supported. Single feature bit is insufficient. Application needs to know how many SF may be used on which PF. >>> Signed-off-by: Xueming Li >>> Acked-by: Viacheslav Ovsiienko >>> Acked-by: Thomas Monjalon [snip]