[prev in list] [next in list] [prev in thread] [next in thread] 

List:       dpdk-dev
Subject:    Re: [dpdk-dev] [PATCH] speed-capabilities: Added Speed Capabilitiestest case
From:       Daniel Kirichok <dkirichok () iol ! unh ! edu>
Date:       2020-06-30 19:59:03
Message-ID: CAFRcHM1QdCp4DLeXniQOiGoEsKbLaMGXmEOT3Ezu7Kqk75uRxQ () mail ! gmail ! com
[Download RAW message or body]

Inline

On Tue, Jun 30, 2020 at 3:27 AM Morten Brørup <mb@smartsharesystems.com>
wrote:

> > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Ivan Dyukov
> > Sent: Tuesday, June 30, 2020 9:03 AM
>
> [...]
>
> > > +Test Case : Speed Capabilities Test
> > > +===================================
> > > +
> > > +1. Use testpmd to retrieve the speed information that the interface
> > is linked at::
> > > +
> > > +      testpmd> show port info <PORT_ID>
> >
> > I'm afraid that testpmd don't show speed_capa value. It shows only
> > link_speed value. to get speed_capa values you should write new
> > ethtool-like application for dpdk interfaces.
>
> That would probably need to be a secondary process, hooking up to the
> testpmd process used for testing. Not the simplest solution.
>
> If testpmd is the primary tool used for testing PMDs, it should support
> all features being tested. In other words: Testpmd needs to be updated, so
> it also shows speed_capa.
>
> I also considered ethtool, but it is only listed under Other Example
> Applications, and has no maintainers. So that does not seem to have a
> promising future.
>
> CC: testpmd Maintainers.
>
> Dan > I have filed a bug report on bugzilla regarding testpmd being
updated for this. I will also look into incorporating the suggestion Ivan
made about the naming convention and organization for the config files.


-- 

Dan Kirichok

UNH InterOperability Laboratory

21 Madbury Rd, Suite 100, Durham, NH 03824

dkirichok@iol.unh.edu

www.iol.unh.edu
[prev in list] [next in list] [prev in thread] [next in thread]