From: David Vodak <vodak@cesnet.cz>
To: web@dpdk.org
Cc: thomas@monjalon.net
Subject: Re: [PATCH] add FlowTest to Known Test Frameworks and Tools
Date: Tue, 30 Jul 2024 14:43:16 +0200 [thread overview]
Message-ID: <8acde081-a9e9-c847-de73-a56507b47e25@cesnet.cz> (raw)
In-Reply-To: <4bd97369-77b2-481e-b656-35fb7d297cc0@cesnet.cz>
Hello Thomas,
could you please take a look at it?
David
On 7/24/24 10:10, David Vodák wrote:
> Hi Thomas,
>
> After my presentation at the DPDK Summit APAC, you suggested that
> FlowTest could be included in the recommended test frameworks and
> tools, which is what I am trying to do in this patch. Could you please
> take a look at this?
>
> Kind regards,
> David Vodak
>
> On 7/17/24 13:24, David Vodak wrote:
>> FlowTest is a complex testbed for testing NetFlow/IPFIX monitoring
>> probes. It includes a traffic generator and player that is capable of
>> simulating traffic of realistic 1/10/100 Gbps networks. Both tools
>> can be used independently of the framework.
>> ---
>> content/testing/_index.md | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/content/testing/_index.md b/content/testing/_index.md
>> index 394287b..3759caf 100644
>> --- a/content/testing/_index.md
>> +++ b/content/testing/_index.md
>> @@ -162,4 +162,5 @@ The testing infrastructure work is coordinated in
>> three complementary forums:
>> - [DPDK Test Suite (DTS)](//git.dpdk.org/tools/dts/)
>> - [ViNePerf](//git.opnfv.org/vineperf/about/)
>> - [OvS PVP perf](//github.com/chaudron/ovs_perf/)
>> +- [FlowTest](//github.com/CESNET/FlowTest)
>> - [downstream projects](//www.dpdk.org/ecosystem/#projects)
next prev parent reply other threads:[~2024-07-30 14:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-17 11:24 David Vodak
2024-07-24 8:10 ` David Vodák
2024-07-30 12:43 ` David Vodak [this message]
2024-07-30 15:52 ` Thomas Monjalon
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=8acde081-a9e9-c847-de73-a56507b47e25@cesnet.cz \
--to=vodak@cesnet.cz \
--cc=thomas@monjalon.net \
--cc=web@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).