From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id CFF0B20F for ; Fri, 27 Mar 2015 12:32:42 +0100 (CET) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga102.jf.intel.com with ESMTP; 27 Mar 2015 04:32:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.11,478,1422950400"; d="scan'208";a="686512363" Received: from bricha3-mobl3.ger.corp.intel.com ([10.243.20.27]) by fmsmga001.fm.intel.com with SMTP; 27 Mar 2015 04:32:39 -0700 Received: by (sSMTP sendmail emulation); Fri, 27 Mar 2015 11:32:38 +0025 Date: Fri, 27 Mar 2015 11:32:38 +0000 From: Bruce Richardson To: Neil Horman Message-ID: <20150327113238.GA11660@bricha3-MOBL3> References: <1427404494-27256-1-git-send-email-bruce.richardson@intel.com> <20150327102956.GB5375@hmsreliant.think-freely.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20150327102956.GB5375@hmsreliant.think-freely.org> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH] mbuf: add comment explaining confusing code 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, 27 Mar 2015 11:32:43 -0000 On Fri, Mar 27, 2015 at 06:29:56AM -0400, Neil Horman wrote: > On Thu, Mar 26, 2015 at 09:14:54PM +0000, Bruce Richardson wrote: > > The logic used in the condition check before freeing an mbuf is > > sometimes confusing, so explain it in a proper comment. > > > > Signed-off-by: Bruce Richardson > > --- > > lib/librte_mbuf/rte_mbuf.h | 10 ++++++++++ > > 1 file changed, 10 insertions(+) > > > > diff --git a/lib/librte_mbuf/rte_mbuf.h b/lib/librte_mbuf/rte_mbuf.h > > index 17ba791..0265172 100644 > > --- a/lib/librte_mbuf/rte_mbuf.h > > +++ b/lib/librte_mbuf/rte_mbuf.h > > @@ -764,6 +764,16 @@ __rte_pktmbuf_prefree_seg(struct rte_mbuf *m) > > { > > __rte_mbuf_sanity_check(m, 0); > > > > + /* > > + * Check to see if this is the last reference to the mbuf. > > + * Note: the double check here is deliberate. If the ref_cnt is "atomic" > > + * the call to "refcnt_update" is a very expensive operation, so we > > + * don't want to call it in the case where we know we are the holder > > + * of the last reference to this mbuf i.e. ref_cnt == 1. > > + * If however, ref_cnt != 1, it's still possible that we may still be > > + * the final decrementer of the count, so we need to check that > > + * result also, to make sure the mbuf is freed properly. > > + */ > > if (likely (rte_mbuf_refcnt_read(m) == 1) || > > likely (rte_mbuf_refcnt_update(m, -1) == 0)) { > > > > -- > > 2.1.0 > > > > > > NAK > the comment is incorrect, a return code of 1 from rte_mbuf_refcnt_read doesn't > guarantee you are the last holder of the buffer if two contexts have a pointer > to it. If two threads have pointers to it, and are both going to free it, the refcnt must be 2 not one, otherwise the refcnt is meaningless. /Bruce > > Zoltans patch is the correct solution here, expensive or not. I wrote up my > explination in this thread: > http://dpdk.org/ml/archives/dev/2015-March/015839.html > >