DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jianfeng Tan <jianfeng.tan@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH] example/vhost: fix failed to allocate mbufs
Date: Sun, 28 Feb 2016 22:40:10 +0100	[thread overview]
Message-ID: <4879300.eaoi2KXdjX@xps13> (raw)
In-Reply-To: <1455754119-121572-1-git-send-email-jianfeng.tan@intel.com>

2016-02-18 08:08, Jianfeng Tan:
> In all, it fails to include master core's mbuf mempool cache.
> 
> Signed-off-by: Jianfeng Tan <jianfeng.tan@intel.com>
> Reported-by: Qian Xu <qian.q.xu@intel.com>

minor note: please keep the "people-tags" in the chronological order.
Here the "Reported-by" is moved before the "Signed-off-by".

[...]
> +* **examples/vhost: fix failed to allocate mbuf.**
> +
> +  vhost-switch often fails to allocate mbuf when dequeue from vring because it
> +  wrongly calculate the number of mbufs needed.

Reworded to comply with release notes style.
Applied, thanks

      reply	other threads:[~2016-02-28 21:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-18  0:08 Jianfeng Tan
2016-02-28 21:40 ` Thomas Monjalon [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=4879300.eaoi2KXdjX@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=jianfeng.tan@intel.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).