From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id EFD372C60 for ; Thu, 21 Mar 2019 14:03:31 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Mar 2019 06:03:30 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,252,1549958400"; d="scan'208";a="309127081" Received: from istokes-mobl1.ger.corp.intel.com (HELO [10.252.18.62]) ([10.252.18.62]) by orsmga005.jf.intel.com with ESMTP; 21 Mar 2019 06:03:28 -0700 To: Ferruh Yigit , dev@dpdk.org Cc: stephen@networkplumber.org, Thomas Monjalon , Andrew Rybchenko References: <1551303948-19746-1-git-send-email-ian.stokes@intel.com> <5e86db4c-215d-ffea-29ee-df026c894627@intel.com> From: Ian Stokes Message-ID: Date: Thu, 21 Mar 2019 13:03:27 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 In-Reply-To: <5e86db4c-215d-ffea-29ee-df026c894627@intel.com> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v1 0/6] ethdev: add min/max MTU to device info X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 21 Mar 2019 13:03:32 -0000 On 3/19/2019 4:30 PM, Ferruh Yigit wrote: > On 2/27/2019 9:45 PM, Ian Stokes wrote: >> Building upon the discussion around [1], this series introduces MTU min >> and MTU max variables. It also provides updates to PMD implementations >> for ixgbe, i40e and IGB devices so that these variables are populated >> for use when retrieving device info. >> >> This series was tested with OVS DPDK and functions as expected for the >> drivers listed below. But a wider selection of PMD drivers would have to >> adopt this to ensure jumbo frames functionality remains for drivers not >> modified in the series. >> >> There is also ongoing discussion in [2] regarding overhead to be >> considered with MTU and how this may change from device to device, this >> series uses existing overhead assumptions. >> >> This series was previously posted as an RFC in [3], this revision >> removes RFC status and implements changes received in feedback. >> >> [1] http://mails.dpdk.org/archives/dev/2018-September/110959.html >> [2] http://mails.dpdk.org/archives/dev/2019-February/124457.html >> [3] http://mails.dpdk.org/archives/dev/2019-February/124938.html >> >> Ian Stokes (5): >> net/i40e: set min and max MTU for i40e devices >> net/i40e: set min and max MTU for i40e VF devices >> net/ixgbe: set min and max MTU for ixgbe devices >> net/ixgbe: set min and max MTU for ixgbe VF devices >> net/e1000: set min and max MTU for igb devices >> >> Stephen Hemminger (1): >> ethdev: add min/max MTU to device info > > Hi Ian, Stephen, > > API and driver updates are included in the patchset, but I believe it would be > good to have some application code that uses it as well, I assume testpmd > already has some code to set MTU, can you please update it too accordingly? > Thanks Ferruh, sure I had looked at this but held off in the v1 as I wasn't sure what best practice was, i.e. introduce the change to sample app now or wait unitl all PMDs were on board. If it's preferred to introduce usage in a sample app then I can do this in the v2. > Also, what do you think starting a unit test (which has a long term target to > verify all ethdev APIs) that tests 'rte_eth_dev_set_mtu()' API with various values? > Sounds useful, I can take a look for the v2, first steps might be basic but can look into it. Ian > In long term all vendors can run this unit test against their HW and verify > ehtdev API implementation of their... > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id DC63CA00E6 for ; Thu, 21 Mar 2019 14:03:33 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id DF3011B4CF; Thu, 21 Mar 2019 14:03:32 +0100 (CET) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by dpdk.org (Postfix) with ESMTP id EFD372C60 for ; Thu, 21 Mar 2019 14:03:31 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Mar 2019 06:03:30 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,252,1549958400"; d="scan'208";a="309127081" Received: from istokes-mobl1.ger.corp.intel.com (HELO [10.252.18.62]) ([10.252.18.62]) by orsmga005.jf.intel.com with ESMTP; 21 Mar 2019 06:03:28 -0700 To: Ferruh Yigit , dev@dpdk.org Cc: stephen@networkplumber.org, Thomas Monjalon , Andrew Rybchenko References: <1551303948-19746-1-git-send-email-ian.stokes@intel.com> <5e86db4c-215d-ffea-29ee-df026c894627@intel.com> From: Ian Stokes Message-ID: Date: Thu, 21 Mar 2019 13:03:27 +0000 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 MIME-Version: 1.0 In-Reply-To: <5e86db4c-215d-ffea-29ee-df026c894627@intel.com> Content-Type: text/plain; charset="UTF-8"; format="flowed" Content-Language: en-US Content-Transfer-Encoding: 7bit Subject: Re: [dpdk-dev] [PATCH v1 0/6] ethdev: add min/max MTU to device info X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 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" Message-ID: <20190321130327.pu60ZRs9FRE4DFcww5tcOosY_4ApguzbvySymkG_-8Y@z> On 3/19/2019 4:30 PM, Ferruh Yigit wrote: > On 2/27/2019 9:45 PM, Ian Stokes wrote: >> Building upon the discussion around [1], this series introduces MTU min >> and MTU max variables. It also provides updates to PMD implementations >> for ixgbe, i40e and IGB devices so that these variables are populated >> for use when retrieving device info. >> >> This series was tested with OVS DPDK and functions as expected for the >> drivers listed below. But a wider selection of PMD drivers would have to >> adopt this to ensure jumbo frames functionality remains for drivers not >> modified in the series. >> >> There is also ongoing discussion in [2] regarding overhead to be >> considered with MTU and how this may change from device to device, this >> series uses existing overhead assumptions. >> >> This series was previously posted as an RFC in [3], this revision >> removes RFC status and implements changes received in feedback. >> >> [1] http://mails.dpdk.org/archives/dev/2018-September/110959.html >> [2] http://mails.dpdk.org/archives/dev/2019-February/124457.html >> [3] http://mails.dpdk.org/archives/dev/2019-February/124938.html >> >> Ian Stokes (5): >> net/i40e: set min and max MTU for i40e devices >> net/i40e: set min and max MTU for i40e VF devices >> net/ixgbe: set min and max MTU for ixgbe devices >> net/ixgbe: set min and max MTU for ixgbe VF devices >> net/e1000: set min and max MTU for igb devices >> >> Stephen Hemminger (1): >> ethdev: add min/max MTU to device info > > Hi Ian, Stephen, > > API and driver updates are included in the patchset, but I believe it would be > good to have some application code that uses it as well, I assume testpmd > already has some code to set MTU, can you please update it too accordingly? > Thanks Ferruh, sure I had looked at this but held off in the v1 as I wasn't sure what best practice was, i.e. introduce the change to sample app now or wait unitl all PMDs were on board. If it's preferred to introduce usage in a sample app then I can do this in the v2. > Also, what do you think starting a unit test (which has a long term target to > verify all ethdev APIs) that tests 'rte_eth_dev_set_mtu()' API with various values? > Sounds useful, I can take a look for the v2, first steps might be basic but can look into it. Ian > In long term all vendors can run this unit test against their HW and verify > ehtdev API implementation of their... >