From mboxrd@z Thu Jan 1 00:00:00 1970 From: Bruce Richardson Subject: Re: [PATCH 2/4] enic: set the max allowed MTU for the NIC Date: Fri, 24 Jun 2016 11:59:19 +0100 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 Cc: dev@dpdk.org To: John Daley 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) Content-Disposition: inline In-Reply-To: <1466140969-5580-3-git-send-email-johndale@cisco.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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