From: "Xu, HuilongX" <huilongx.xu@intel.com>
To: "Liu, Yong" <yong.liu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] update dump test suite
Date: Wed, 10 Aug 2016 07:50:49 +0000 [thread overview]
Message-ID: <DF2A19295B96364286FEB7F3DDA27A4637B90CA0@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <57A9A8DE.9030704@intel.com>
Hi yong,
The mempool name maybe will changed, when development want to update.
Dump only a debug function, I think we only check it can dump the info.
And the info by dump is normal or not decide by mempool auto test and mempool struct.
Thanks a lot
> -----Original Message-----
> From: Liu, Yong
> Sent: Tuesday, August 09, 2016 5:57 PM
> To: Xu, HuilongX; dts@dpdk.org
> Subject: Re: [dts] [PATCH V1] update dump test suite
>
> Huilong,
> dump_ring, dump_mempool are the test cases for dpdk API which can dump
> all mempools and rings.
> Ideally, we need to verify dumped mempool information is the same as
> added. But at least, we need to verify all added mempools and rings can
> be dumped.
> After running mempool autotest, there' re three mempools left, they are
> "test_nocache", "test_cache", "test_stack".
> We need verify the information is correct.
>
>
> On 08/09/2016 01:47 PM, Xu, HuilongX wrote:
> >> Only check ring number is not enough, we'd better also check expected
> >> >ring name.
> > The ring name only a string. The string content set by who will used
> it.
> > So I think we don't need check the string content. We only should
> check dump can work, and get ring struct info.
> > And the struct content by dpdk decision.
> >> >
prev parent reply other threads:[~2016-08-10 7:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-08 8:11 xu,huilong
2016-08-09 5:14 ` Liu, Yong
2016-08-09 5:47 ` Xu, HuilongX
2016-08-09 9:56 ` Liu, Yong
2016-08-10 7:50 ` Xu, HuilongX [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=DF2A19295B96364286FEB7F3DDA27A4637B90CA0@SHSMSX101.ccr.corp.intel.com \
--to=huilongx.xu@intel.com \
--cc=dts@dpdk.org \
--cc=yong.liu@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).