From: Angela Czubak <aczubak@caviumnetworks.com>
To: dts@dpdk.org
Subject: [dts] TestSuite_l2fwd.py questions
Date: Mon, 3 Apr 2017 18:11:21 +0200 [thread overview]
Message-ID: <877130cc-6b94-1ecd-693c-b09fda2a55eb@caviumnetworks.com> (raw)
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
next reply other threads:[~2017-04-03 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-03 16:11 Angela Czubak [this message]
2017-04-05 1:35 ` Liu, Yong
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=877130cc-6b94-1ecd-693c-b09fda2a55eb@caviumnetworks.com \
--to=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).