From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v5 7/8]i40e:support VxLAN Tx checksum offload Date: Thu, 16 Oct 2014 22:34:09 +0200 Message-ID: <2679158.ldaB3mIRM3@xps13> References: <1413006935-22535-1-git-send-email-jijiang.liu@intel.com> <1413006935-22535-8-git-send-email-jijiang.liu@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev-VfR2kkLFssw@public.gmane.org To: Jijiang Liu Return-path: In-Reply-To: <1413006935-22535-8-git-send-email-jijiang.liu-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces-VfR2kkLFssw@public.gmane.org Sender: "dev" 2014-10-11 13:55, Jijiang Liu: > Support VxLAN Tx checksum offload, which include > - outer L3(IP) checksum offload > - inner L3(IP) checksum offload > - inner L4(UDP, TCP and SCTP) checksum offload [...] > + > + /* fields to support tunnelling packet TX offloads */ I know that previous comment is "fields to support TX offloads", but I'd prefer "for TX offloading of tunnels". Maybe that "encapsulation" is better than "tunnel". Just my opinion. > + union { > + /**< combined inner l2/l3 lengths as single var */ > + uint16_t inner_l2_l3_len; > + > + struct { > + /**< inner L3 (IP) Header Length. */ > + uint16_t inner_l3_len:9; > + > + /**< L2 (MAC) Header Length. */ > + uint16_t inner_l2_len:7; > + }; > + }; I would like to highlight that you are using 2 bytes in the second cache line of the mbuf. It deserves at least a line in the commit log. Actually I'd prefer a separate patch for mbuf modifications. Thanks -- Thomas