test suite reviews and discussions
 help / color / mirror / Atom feed
From: "Liu, Yong" <yong.liu@intel.com>
To: Jianbo Liu <jianbo.liu@linaro.org>
Cc: "Lu, PeipeiX" <peipeix.lu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH V1] tests/unit_tests_lpm: Add the size of the judgment hugepage
Date: Tue, 17 Oct 2017 14:16:48 +0000	[thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E62EF7FC2@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <CAP4Qi3_dEc5aGLQvCaKBtM3ObLUebmsCB0xX5RwByR8zveXoxw@mail.gmail.com>

Jianbo,
Look like this patch only impacted lpm6_autotest. 
I remembered that lpm_perf_autotest required for huge memories for millions of entries.
Just checked with latest version, there's no such requirement now. Will remove the limitation in unit_test_lpm suite.
Thanks for reminder.

Thanks,
Marvin 

> -----Original Message-----
> From: Jianbo Liu [mailto:jianbo.liu@linaro.org]
> Sent: Tuesday, October 17, 2017 2:27 PM
> To: Liu, Yong <yong.liu@intel.com>
> Cc: Lu, PeipeiX <peipeix.lu@intel.com>; dts@dpdk.org
> Subject: Re: [dts] [PATCH V1] tests/unit_tests_lpm: Add the size of the
> judgment hugepage
> 
> Hi Yong,
> 
> Can you tell me what the failed cases are? I don't think it need 8G memory.
> 
> Thanks!
> Jianbo
> 
> On 16 October 2017 at 15:53, Liu, Yong <yong.liu@intel.com> wrote:
> > Jianbo,
> > Only lpm unit test required for so much memory. If there's not enough
> resource for some cases, this kind of cases should be taken as failed. The
> error reason has been included in the message, so user can choose either
> enlarge DUT resource and rerun or just ignore it
> >
> > Thanks,
> > Marvin
> >
> >> -----Original Message-----
> >> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Jianbo Liu
> >> Sent: Wednesday, October 11, 2017 3:23 PM
> >> To: Lu, PeipeiX <peipeix.lu@intel.com>
> >> Cc: dts@dpdk.org
> >> Subject: Re: [dts] [PATCH V1] tests/unit_tests_lpm: Add the size of the
> >> judgment hugepage
> >>
> >> Hi Peipei,
> >>
> >> Is there any requirement that the total hugepages should be larger than
> 8G?
> >> Besides, self.verify will exit this test, not raise one warning as you
> >> declared. Could it be wrong?
> >>
> >> Thanks!
> >> Jianbo
> >>
> >> On 6 September 2017 at 16:05, lu,peipei <peipeix.lu@intel.com> wrote:
> >> > Check whether host hugepage fulfill the requirement.If host setup
> can't
> >> run this case, just raise one warning
> >> >
> >> > Signed-off-by: lu,peipei <peipeix.lu@intel.com>
> >> > ---
> >> >  tests/TestSuite_unit_tests_lpm.py | 15 ++++++---------
> >> >  1 file changed, 6 insertions(+), 9 deletions(-)
> >> >
> >> > diff --git a/tests/TestSuite_unit_tests_lpm.py
> >> b/tests/TestSuite_unit_tests_lpm.py
> >> > index e8149ff..f9a2bf7 100644
> >> > --- a/tests/TestSuite_unit_tests_lpm.py
> >> > +++ b/tests/TestSuite_unit_tests_lpm.py
> >> > @@ -81,21 +81,18 @@ class TestUnitTestsLpmIpv6(TestCase):
> >> >          """
> >> >          [arch, machine, env, toolchain] = self.target.split('-')
> >> >          self.verify(arch in ["x86_64", "arm64"], "lpm6 request huge
> >> memory")
> >> > -        if env == 'bsdapp':
> >> > +        hugepages_size = int(self.dut.send_expect("awk
> '/Hugepagesize/
> >> {print $2}' /proc/meminfo", "# "))
> >> > +       hugepage_ori = self.dut.get_total_huge_pages()
> >> > +       if env == 'bsdapp':
> >> >              pass
> >> >          else:
> >> > -            hugepage_ori = self.dut.get_total_huge_pages()
> >> > -            self.dut.set_huge_pages(4096)
> >> > -            hugepage_num = self.dut.get_total_huge_pages()
> >> > -            self.verify(hugepage_num >= 4096, "failed to request
> huge
> >> memory")
> >> > +           hugepage_8G = 8 * 1024 * 1024
> >> > +            total_hugepage = hugepages_size * hugepage_ori
> >> > +            self.verify(total_hugepage >= hugepage_8G,"have no
> enough
> >> hugepage")
> >> >
> >> >          self.dut.send_expect("./%s/app/test -n 1 -c f" % self.target,
> >> "R.*T.*E.*>.*>", 60)
> >> >          out = self.dut.send_expect("lpm6_autotest", "RTE>>", 3600)
> >> >          self.dut.send_expect("quit", "# ")
> >> > -        if env == 'bsdapp':
> >> > -            pass
> >> > -        else:
> >> > -            self.dut.set_huge_pages(hugepage_ori)
> >> >          self.verify("Test OK" in out, "Test failed")
> >> >
> >> >      def tear_down(self):
> >> > --
> >> > 1.9.3
> >> >

      reply	other threads:[~2017-10-17 14:17 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-06  8:05 lu,peipei
2017-09-07 11:05 ` Liu, Yong
2017-10-11  7:23 ` Jianbo Liu
2017-10-16  7:53   ` Liu, Yong
2017-10-17  6:26     ` Jianbo Liu
2017-10-17 14:16       ` Liu, Yong [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=86228AFD5BCD8E4EBFD2B90117B5E81E62EF7FC2@SHSMSX103.ccr.corp.intel.com \
    --to=yong.liu@intel.com \
    --cc=dts@dpdk.org \
    --cc=jianbo.liu@linaro.org \
    --cc=peipeix.lu@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).