From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v4 08/21] mbuf: extend fdir field Date: Tue, 28 Oct 2014 14:28:03 +0100 Message-ID: <1914722.TcObfZY1uh@xps13> References: <1411711418-12881-1-git-send-email-jingjing.wu@intel.com> <1413939687-11177-1-git-send-email-jingjing.wu@intel.com> <1413939687-11177-9-git-send-email-jingjing.wu@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev-VfR2kkLFssw@public.gmane.org To: Jingjing Wu Return-path: In-Reply-To: <1413939687-11177-9-git-send-email-jingjing.wu-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-22 09:01, Jingjing Wu: > extend fdir field to support flex bytes reported when fdir match The commit log should explain why it is required (i40e?). It will help to understand when digging into git history of mbuf file. > --- a/lib/librte_mbuf/rte_mbuf.h > +++ b/lib/librte_mbuf/rte_mbuf.h > @@ -171,8 +173,14 @@ struct rte_mbuf { > union { > uint32_t rss; /**< RSS hash result if RSS enabled */ > struct { > - uint16_t hash; > - uint16_t id; > + union { > + struct { > + uint16_t hash; > + uint16_t id; > + }; > + uint32_t lo; /**< flexible bytes low*/ > + }; > + uint32_t hi; /**< flexible bytes high*/ > } fdir; /**< Filter identifier if FDIR enabled */ Please explain what could be the data of "flexible bytes high". -- Thomas