DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Nelson Escobar <neescoba@cisco.com>
Cc: dev@dpdk.org, johndale@cisco.com
Subject: Re: [dpdk-dev] [PATCH] enic: fix releasing of mbufs when tearing down rq
Date: Thu, 23 Jun 2016 12:41:32 +0100	[thread overview]
Message-ID: <20160623114132.GI5024@bricha3-MOBL3> (raw)
In-Reply-To: <1465948534-14427-1-git-send-email-neescoba@cisco.com>

On Tue, Jun 14, 2016 at 04:55:34PM -0700, Nelson Escobar wrote:
> When trying to release the mbufs, the function was incorrectly
> iterating over the max size configured instead of the actual size
> of the ring.
> 
> Fixes: cbb44dddcade ("enic: receive path performance improvements")
> 
> Signed-off-by: Nelson Escobar <neescoba@cisco.com>
> Reviewed-by: John Daley <johndale@cisco.com>

Applied to dpdk-next-net/rel_16_07 with corrected fixes line.

/Bruce

      reply	other threads:[~2016-06-23 11:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-14 23:55 Nelson Escobar
2016-06-23 11:41 ` Bruce Richardson [this message]

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=20160623114132.GI5024@bricha3-MOBL3 \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=johndale@cisco.com \
    --cc=neescoba@cisco.com \
    /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).