From: Thomas Monjalon <thomas@monjalon.net>
To: Daniel Kirichok <dkirichok@iol.unh.edu>
Cc: dts@dpdk.org, dev@dpdk.org, Lincoln Lavoie <lylavoie@iol.unh.edu>,
david.marchand@redhat.com, ferruh.yigit@intel.com,
arybchenko@solarflare.com, mb@smartsharesystems.com,
i.dyukov@samsung.com, rasland@mellanox.com, j.hendergart@f5.com
Subject: Re: [dpdk-dev] Speed Capabilities Feature
Date: Wed, 24 Jun 2020 21:55:07 +0200 [thread overview]
Message-ID: <9145227.bPS0MTqRLS@thomas> (raw)
In-Reply-To: <CAFRcHM3J40Ta-dZVeAZtQzd=R_NPdDzAn3Jx+roRhb-NBKT+Eg@mail.gmail.com>
Hi,
A bit of context: Daniel is going to implement a test in DTS
for ethdev speed capability:
http://doc.dpdk.org/guides/nics/features.html#speed-capabilities
24/06/2020 21:32, Daniel Kirichok:
> The Speed Capabilities test will first check the speed of each interface
> that the device lists through ethtool.
I assume you mean doing a query in Linux before starting DPDK.
> Then it compares each interface
> speed to a user-defined set of expected speeds set in a newly created
> config file, `speed_capabilities.cfg`.
Why do you need such config file?
> The test fails if an interface is
> found that isn’t accounted for in the cfg file, the detected speed is less
> than 1 Gb/s, or an interface detects a different speed than what is
> expected from the cfg file. Otherwise, it passes.
So you don't test DPDK?
Would be interesting to compare the actual link speed
from rte_eth_link_get() with the advertised capability.
What else do we want to test regarding link speed? autonegotiation?
next prev parent reply other threads:[~2020-06-24 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 19:32 [dpdk-dev] Speed Capabilities Feature Daniel Kirichok
2020-06-24 19:55 ` Thomas Monjalon [this message]
2020-06-24 20:01 ` Lincoln Lavoie
2020-06-24 20:09 ` Thomas Monjalon
2020-06-25 7:52 ` Morten Brørup
2020-06-25 20:04 ` Daniel Kirichok
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=9145227.bPS0MTqRLS@thomas \
--to=thomas@monjalon.net \
--cc=arybchenko@solarflare.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=dkirichok@iol.unh.edu \
--cc=dts@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=i.dyukov@samsung.com \
--cc=j.hendergart@f5.com \
--cc=lylavoie@iol.unh.edu \
--cc=mb@smartsharesystems.com \
--cc=rasland@mellanox.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.