From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 1C9CEC68A for ; Fri, 24 Jun 2016 12:59:25 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga103.fm.intel.com with ESMTP; 24 Jun 2016 03:59:24 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.26,520,1459839600"; d="scan'208";a="724416921" Received: from singalsu-mobl4.ger.corp.intel.com ([10.252.31.226]) by FMSMGA003.fm.intel.com with SMTP; 24 Jun 2016 03:59:23 -0700 Received: by (sSMTP sendmail emulation); Fri, 24 Jun 2016 11:59:19 +0025 Date: Fri, 24 Jun 2016 11:59:19 +0100 From: Bruce Richardson To: John Daley Cc: dev@dpdk.org Message-ID: <20160624105919.GD13456@bricha3-MOBL3> References: <1466140969-5580-1-git-send-email-johndale@cisco.com> <1466140969-5580-3-git-send-email-johndale@cisco.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1466140969-5580-3-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 2/4] enic: set the max allowed MTU for the NIC 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: Fri, 24 Jun 2016 10:59:26 -0000 On Thu, Jun 16, 2016 at 10:22:47PM -0700, John Daley wrote: > The max MTU is set to the max egress packet size allowed by the VIC > minus the size of a an IPv4 L2 header with .1Q (18 bytes). > I think a bit more detail might be needed here. For example: * What was the MTU set to by default before this patch is applied? Was it just set to 1518 or something else? * What happens, if anything, if buffers bigger than the MTU size are sent down? /Bruce