From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 712792BA9 for ; Wed, 29 Jun 2016 12:01:37 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga101.jf.intel.com with ESMTP; 29 Jun 2016 03:01:37 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,546,1459839600"; d="scan'208";a="726743204" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.220.81]) by FMSMGA003.fm.intel.com with SMTP; 29 Jun 2016 03:01:34 -0700 Received: by (sSMTP sendmail emulation); Wed, 29 Jun 2016 11:01:33 +0025 Date: Wed, 29 Jun 2016 11:01:33 +0100 From: Bruce Richardson To: John Daley Cc: dev@dpdk.org Message-ID: <20160629100132.GD4720@bricha3-MOBL3> References: <20160624110103.GE13456@bricha3-MOBL3> <1466807368-7215-1-git-send-email-johndale@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1466807368-7215-1-git-send-email-johndale@cisco.com> Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?= =?iso-8859-1?Q?opment?= Ireland Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Subject: Re: [dpdk-dev] [PATCH v2 1/2] enic: determine max egress packet size and max MTU X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2016 10:01:37 -0000 On Fri, Jun 24, 2016 at 03:29:27PM -0700, John Daley wrote: > Pull in common VNIC code which enables querying for max egress > packet size with newer firmware via a device command. If the > field is non-zero, it is the max egress packet size. If it is > 0, the default value (9022) can safely be assumed. The value > for 1300 series VICS using firmware versions >= 3.1.2 for blade > series and >= 2.0.13 for rack series servers is 9208. > > Tx buffers can be emitted only if they are less than the max egress > packet size regardless of the MTU setting (the MTU is advisory). > The max egress packet size can used to determine the upper limit > of the MTU since the enic can also receive packets of size greater > than max egress packet size. A max_mtu variable is added with > a value of max egress packet size minus L2 header size. > > The default MTU is set via the CIMC/UCSM management interface and > currently allows value up to 9000. If the value is changed, the > host must be reboot. To avoid the reboot and allow MTU values > up to the max capability of the NIC, MTU update capability will > be added with a max value capped by max_mtu. > > Signed-off-by: John Daley > --- > v2: Squished patch 1/4 and 2/4 into one. Tried to do a little > better explanaiton of the intent of the patch in the commit > message. > Patchset applied to dpdk-next-net/rel_16_07 /Bruce