From: Lincoln Lavoie <lylavoie@iol.unh.edu>
To: Aida.Farahjooyanarjan@t-systems.com
Cc: ci@dpdk.org
Subject: Re: [dpdk-ci] Testing DPDK on Bare metal
Date: Thu, 11 Feb 2021 20:56:08 -0500 [thread overview]
Message-ID: <CAOE1vsM07xn=Wn852wSGK_wSr1yrmhML10aTaFupu770UwQMKw@mail.gmail.com> (raw)
In-Reply-To: <FR2P281MB0281AEBF43D7E605803A3326AF8D9@FR2P281MB0281.DEUP281.PROD.OUTLOOK.COM>
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
Hello Aida,
For testing, I would look into setting up two servers, according to the
documentation in the DPDK Test Suite (DTS), https://doc.dpdk.org/dts/gsg/
The physical setup for basic testing is fairly symmetric, with NICs in each
server connected back to back. DTS leverages some tooling/examples
included with DPDK, such testpmd, along with external traffic generators
like TRex. This is what we use is most of the community lab setup.
Cheers,
Lincoln
On Thu, Feb 11, 2021 at 6:30 PM <Aida.Farahjooyanarjan@t-systems.com> wrote:
> Hello All,
>
>
>
> I would like to install DPDK on our Bare metal servers to run the
> performance test as well as a functional test. Could you please provide me
> a support from your side at least send us a useful manual?
>
>
>
> Viele Grüße
>
> Aida
>
>
>
--
*Lincoln Lavoie*
Principal Engineer, Broadband Technologies
21 Madbury Rd., Ste. 100, Durham, NH 03824
lylavoie@iol.unh.edu
https://www.iol.unh.edu
+1-603-674-2755 (m)
<https://www.iol.unh.edu>
[-- Attachment #2: Type: text/html, Size: 2917 bytes --]
prev parent reply other threads:[~2021-02-12 1:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 13:54 Aida.Farahjooyanarjan
2021-02-12 1:56 ` Lincoln Lavoie [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='CAOE1vsM07xn=Wn852wSGK_wSr1yrmhML10aTaFupu770UwQMKw@mail.gmail.com' \
--to=lylavoie@iol.unh.edu \
--cc=Aida.Farahjooyanarjan@t-systems.com \
--cc=ci@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).