dev.dpdk.org archive mirror
 help / color / mirror / Atom feed
From: "Wiles, Keith" <keith.wiles-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
To: Zoltan Kiss <zoltan.kiss-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>,
	"dev-VfR2kkLFssw@public.gmane.org"
	<dev-VfR2kkLFssw@public.gmane.org>
Subject: Re: [PATCH] mbuf: optimize refcnt handling during free
Date: Thu, 26 Mar 2015 21:00:33 +0000	[thread overview]
Message-ID: <D139DD49.19B82%keith.wiles@intel.com> (raw)
In-Reply-To: <1427393457-7080-1-git-send-email-zoltan.kiss-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>



On 3/26/15, 1:10 PM, "Zoltan Kiss" <zoltan.kiss-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org> wrote:

>The current way is not the most efficient: if m->refcnt is 1, the second
>condition never evaluates, and we set it to 0. If refcnt > 1, the 2nd
>condition fails again, although the code suggest otherwise to branch
>prediction. Instead we should keep the second condition only, and remove
>the
>duplicate set to zero.
>
>Signed-off-by: Zoltan Kiss <zoltan.kiss-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
>---
> lib/librte_mbuf/rte_mbuf.h | 5 +----
> 1 file changed, 1 insertion(+), 4 deletions(-)
>
>diff --git a/lib/librte_mbuf/rte_mbuf.h b/lib/librte_mbuf/rte_mbuf.h
>index 17ba791..3ec4024 100644
>--- a/lib/librte_mbuf/rte_mbuf.h
>+++ b/lib/librte_mbuf/rte_mbuf.h
>@@ -764,10 +764,7 @@ __rte_pktmbuf_prefree_seg(struct rte_mbuf *m)
> {
> 	__rte_mbuf_sanity_check(m, 0);
> 
>-	if (likely (rte_mbuf_refcnt_read(m) == 1) ||
>-			likely (rte_mbuf_refcnt_update(m, -1) == 0)) {
>-
>-		rte_mbuf_refcnt_set(m, 0);
>+	if (likely (rte_mbuf_refcnt_update(m, -1) == 0)) {
> 
> 		/* if this is an indirect mbuf, then
> 		 *  - detach mbuf

I fell for this one too, but read Bruce¹s email
http://dpdk.org/ml/archives/dev/2015-March/014481.html
>-- 
>1.9.1
>

  parent reply	other threads:[~2015-03-26 21:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-26 18:10 [PATCH] mbuf: optimize refcnt handling during free Zoltan Kiss
     [not found] ` <1427393457-7080-1-git-send-email-zoltan.kiss-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
2015-03-26 21:00   ` Wiles, Keith [this message]
     [not found]     ` <D139DD49.19B82%keith.wiles-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2015-03-26 21:07       ` Bruce Richardson
2015-03-27 10:25       ` Neil Horman
     [not found]         ` <20150327102533.GA5375-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2015-03-27 10:48           ` Ananyev, Konstantin
     [not found]             ` <2601191342CEEE43887BDE71AB97725821407F18-pww93C2UFcwu0RiL9chJVbfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2015-03-27 12:44               ` Neil Horman
     [not found]                 ` <20150327124451.GE5375-B26myB8xz7F8NnZeBjwnZQMhkBWG/bsMQH7oEaQurus@public.gmane.org>
2015-03-27 13:10                   ` Olivier MATZ
     [not found]                     ` <551556C9.6030609-pdR9zngts4EAvxtiuMwx3w@public.gmane.org>
2015-03-27 13:16                       ` Bruce Richardson
2015-03-27 13:22                         ` Ananyev, Konstantin
2015-03-27 10:50           ` Olivier MATZ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D139DD49.19B82%keith.wiles@intel.com \
    --to=keith.wiles-ral2jqcrhueavxtiumwx3w@public.gmane.org \
    --cc=dev-VfR2kkLFssw@public.gmane.org \
    --cc=zoltan.kiss-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).