From mboxrd@z Thu Jan 1 00:00:00 1970 From: Maxime Coquelin Subject: Re: [PATCH 1/2] mbuf: add rte_pktmbuff_reset_headroom function Date: Tue, 4 Oct 2016 13:51:39 +0200 Message-ID: <41ca04b5-26d6-20eb-baf2-6a34fc003d2b@redhat.com> References: <1475151633-6785-1-git-send-email-maxime.coquelin@redhat.com> <8b1847c7-e1a7-7477-8937-1e49c3ec0a8f@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Cc: stephen@networkplumber.org, mst@redhat.com, yuanhan.liu@linux.intel.com To: Olivier Matz , dev@dpdk.org Return-path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 512B72A6C for ; Tue, 4 Oct 2016 13:51:44 +0200 (CEST) In-Reply-To: <8b1847c7-e1a7-7477-8937-1e49c3ec0a8f@6wind.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 10/03/2016 06:11 PM, Olivier Matz wrote: > Hi Maxime, > > On 09/29/2016 02:20 PM, Maxime Coquelin wrote: >> Some application use rte_mbuf_raw_alloc() function to improve >> performance by not resetting mbuf's fields to their default state. >> >> This can be however problematic for mbuf consumers that need some >> headroom, meaning that data_off field gets decremented after >> allocation. When the mbuf is re-used afterwards, there might not >> be enough room for the consumer to prepend anything, if the data_off >> field is not reset to its default value. >> >> This patch adds a new rte_pktmbuf_reset_headroom() function that >> applications can call to reset the data_off field. >> This patch also replaces current data_off affectations in the mbuf >> lib with a call to this function. >> >> Signed-off-by: Maxime Coquelin > > Sounds like a good idea. Just one small comment below. > >> >> /** >> + * Reset the data_off field of a packet mbuf to its default value. >> + * >> + * The given mbuf must have only one segment. >> + * >> + * @param m >> + * The packet mbuf's data_off field has to be reset. >> + */ >> +static inline void rte_pktmbuf_reset_headroom(struct rte_mbuf *m) >> +{ >> + m->data_off = RTE_MIN(RTE_PKTMBUF_HEADROOM, (uint16_t)m->buf_len); >> +} > > Maybe we should also highlight in the API comment that the segment > should be empty. Good point. I'll change to: The given mbuf must have only one segment, which should be empty. Thanks, Maxime