From: "Liu, Yong" <yong.liu@intel.com>
To: Angela Czubak <aczubak@caviumnetworks.com>,
"dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] TestSuite_l2fwd.py questions
Date: Wed, 5 Apr 2017 01:35:06 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E62DB26B2@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <877130cc-6b94-1ecd-693c-b09fda2a55eb@caviumnetworks.com>
Hi Angela,
L2fwd case was designed few years ago. At that time we forced l2fwd case using different ports on different cards for maximum throughput.
Currently all performance reports are based on l3fwd sample, so you can look at L3fwd test case for replacement.
For the mismatched expected output, that maybe one bug. We haven't run l2fwd performance case for a long time.
Thanks,
Marvin
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Angela Czubak
> Sent: Tuesday, April 04, 2017 12:11 AM
> To: dts@dpdk.org
> Subject: [dts] TestSuite_l2fwd.py questions
>
> Hi,
>
> I was looking into L2fwd test case and was wondering if getting
> available ports (self.dut_ports = self.dut.get_ports_performance() in
> set_up_all() method) and leaving the default for force_different_nic
> argument was on purpose. I mean, was this test designed to run for two
> different NICs only?
>
> One more question: why does test_l2fwd integrity run l2fwd and expect
> "memory mapped" in the output, whereas others seem to expect "L2FWD:
> entering main loop"? Is that a bug?
>
> Regards,
>
> Angela Czubak
prev parent reply other threads:[~2017-04-05 1:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 16:11 Angela Czubak
2017-04-05 1:35 ` 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=86228AFD5BCD8E4EBFD2B90117B5E81E62DB26B2@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=aczubak@caviumnetworks.com \
--cc=dts@dpdk.org \
/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).