From: Thomas Monjalon <thomas@monjalon.net>
To: gregory@weka.io
Cc: dev@dpdk.org, Olivier Matz <olivier.matz@6wind.com>
Subject: Re: [dpdk-dev] [PATCH v3] mbuf: fix bulk allocation when debug enabled
Date: Wed, 10 May 2017 18:17:31 +0200 [thread overview]
Message-ID: <2707890.iNWbliFgfp@xps> (raw)
In-Reply-To: <20170510151310.20505-1-olivier.matz@6wind.com>
10/05/2017 17:13, Olivier Matz:
> From: Gregory Etelson <gregory@weka.io>
>
> The debug assertions when allocating a raw mbuf are not correct since
> commit 8f094a9ac5d7 ("mbuf: set mbuf fields while in pool"),
> which triggers a panic when using this function in debug mode
>
> Change the expected number of segments to 1 instead of 0, and
> factorize these sanity checks.
>
> Fixes: 8f094a9ac5d7 ("mbuf: set mbuf fields while in pool")
>
> Signed-off-by: Gregory Etelson <gregory@weka.io>
> Signed-off-by: Olivier Matz <olivier.matz@6wind.com>
Applied, thanks
prev parent reply other threads:[~2017-05-10 16:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-06 7:26 [dpdk-dev] [PATCH v2] " Gregory Etelson
2017-05-10 14:42 ` Olivier Matz
2017-05-10 14:54 ` Thomas Monjalon
2017-05-10 15:13 ` [dpdk-dev] [PATCH v3] " Olivier Matz
2017-05-10 16:17 ` 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=2707890.iNWbliFgfp@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=gregory@weka.io \
--cc=olivier.matz@6wind.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).