From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 4D4BF2BAE for ; Tue, 9 Aug 2016 11:53:37 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga104.fm.intel.com with ESMTP; 09 Aug 2016 02:53:36 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.28,494,1464678000"; d="scan'208";a="1022242815" Received: from stv-crb-56.sh.intel.com (HELO [10.239.128.116]) ([10.239.128.116]) by fmsmga001.fm.intel.com with ESMTP; 09 Aug 2016 02:53:36 -0700 Message-ID: <57A9A8DE.9030704@intel.com> Date: Tue, 09 Aug 2016 17:56:46 +0800 From: "Liu, Yong" User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: "Xu, HuilongX" , "dts@dpdk.org" References: <1470643881-3347-1-git-send-email-huilongx.xu@intel.com> <86228AFD5BCD8E4EBFD2B90117B5E81E2226B626@SHSMSX103.ccr.corp.intel.com> In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [dts] [PATCH V1] update dump test suite X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Aug 2016 09:53:37 -0000 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. >> >