From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Michal Jastrzebski <michalx.k.jastrzebski@intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] test: fix test_tlb_tx_burst
Date: Mon, 10 Aug 2015 16:13:39 +0200 [thread overview]
Message-ID: <21172092.tDjSpFFvHW@xps13> (raw)
In-Reply-To: <1438949731-17748-1-git-send-email-michalx.k.jastrzebski@intel.com>
> Test failed on verification if number of bytes
> transmitted on each slave is not less than 90%
> and greater than 110% of mean value of bytes transmitted
> thru one slave. This was verified on a real system
> but is difficult to achieve using virtualpmd.
> That's why for unit tests only, it is sufficient to verify that with
> high load (2 seconds transsmission) all slaves are trasnitting
> so the traffic is balanced.
>
> v2 changes:
> - improved description
> - reverted number of packets generated (in v1 it was decreased,
> but to achieve balancing it has to be high load).
>
> Signed-off-by: Michal Jastrzebski <michalx.k.jastrzebski@intel.com>
Fixes: 0c8396e6d786 ("bond: unit tests for mode 5")
Applied thanks
prev parent reply other threads:[~2015-08-10 14:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-07 12:15 Michal Jastrzebski
2015-08-10 14:13 ` Thomas Monjalon [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=21172092.tDjSpFFvHW@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=michalx.k.jastrzebski@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).