From: Thomas Monjalon <thomas@monjalon.net>
To: Alejandro Lucero <alejandro.lucero@netronome.com>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
dev@dpdk.org, Shepard Siegel <shepard.siegel@atomicrules.com>,
Ed Czeck <ed.czeck@atomicrules.com>,
John Miller <john.miller@atomicrules.com>,
John McNamara <john.mcnamara@intel.com>,
Harish Patil <harish.patil@cavium.com>,
Rasesh Mody <rasesh.mody@cavium.com>,
Rahul Lakkireddy <rahul.lakkireddy@chelsio.com>,
Hemant Agrawal <hemant.agrawal@nxp.com>,
Shreyansh Jain <shreyansh.jain@nxp.com>,
Wenzhuo Lu <wenzhuo.lu@intel.com>,
Marcin Wojtas <mw@semihalf.com>,
Michal Krawczyk <mk@semihalf.com>,
Guy Tzalik <gtzalik@amazon.com>,
Evgeny Schemeilin <evgenys@amazon.com>,
Jing Chen <jing.d.chen@intel.com>,
Helin Zhang <helin.zhang@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
Konstantin Ananyev <konstantin.ananyev@intel.com>,
Adrien Mazarguil <adrien.mazarguil@6wind.com>,
Nelio Laranjeiro <nelio.laranjeiro@6wind.com>,
Matej Vido <vido@cesnet.cz>,
Pascal Mazon <pascal.mazon@6wind.com>,
Yuanhan Liu <yuanhan.liu@linux.intel.com>,
Maxime Coquelin <maxime.coquelin@redhat.com>,
Shrikrishna Khare <skhare@vmware.com>
Subject: Re: [dpdk-dev] [PATCH] drivers/net: document missing speed capabilities feature
Date: Tue, 16 May 2017 12:02:57 +0200 [thread overview]
Message-ID: <3454007.3ZDP6eXIq0@xps> (raw)
In-Reply-To: <CAD+H993bAMOFMOBqro3GnQjj-8FLyj4OswkXYY77mjK=1=aLxQ@mail.gmail.com>
16/05/2017 11:39, Alejandro Lucero:
> Maybe we need another feature for detected link speed report capability.
>
> There is already support for ETH_SPEED_NUM_NONE if the speed is not defined
> or it can not be specified by the device. Netronome has some firmwares
> without that link speed report capability, although maybe we are not the
> only ones with that problem.
>
>
> What do you think about this?
Yes, you mean you can advertise a speed capability,
but cannot report the real negotiated speed, right?
So we could add this feature.
There are also virtual drivers which cannot report some real speed.
next prev parent reply other threads:[~2017-05-16 10:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 13:10 Ferruh Yigit
2017-05-10 13:49 ` Mcnamara, John
2017-05-10 13:51 ` Thomas Monjalon
2017-05-12 10:49 ` Ferruh Yigit
2017-05-12 15:48 ` Thomas Monjalon
2017-05-15 8:40 ` Ferruh Yigit
2017-05-15 9:33 ` Thomas Monjalon
2017-05-16 9:39 ` Alejandro Lucero
2017-05-16 10:02 ` Thomas Monjalon [this message]
2017-05-16 10:17 ` Alejandro Lucero
2017-05-15 10:59 ` [dpdk-dev] [PATCH v2] " Ferruh Yigit
2017-05-15 12:17 ` Pascal Mazon
2017-05-15 12:23 ` Ferruh Yigit
2017-05-15 12:30 ` [dpdk-dev] [PATCH v3] " Ferruh Yigit
2017-05-17 13:28 ` Mcnamara, John
2017-06-12 15:48 ` Ferruh Yigit
2017-05-16 9:00 ` [dpdk-dev] [PATCH v2] " Mcnamara, John
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=3454007.3ZDP6eXIq0@xps \
--to=thomas@monjalon.net \
--cc=adrien.mazarguil@6wind.com \
--cc=alejandro.lucero@netronome.com \
--cc=dev@dpdk.org \
--cc=ed.czeck@atomicrules.com \
--cc=evgenys@amazon.com \
--cc=ferruh.yigit@intel.com \
--cc=gtzalik@amazon.com \
--cc=harish.patil@cavium.com \
--cc=helin.zhang@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jing.d.chen@intel.com \
--cc=jingjing.wu@intel.com \
--cc=john.mcnamara@intel.com \
--cc=john.miller@atomicrules.com \
--cc=konstantin.ananyev@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=mk@semihalf.com \
--cc=mw@semihalf.com \
--cc=nelio.laranjeiro@6wind.com \
--cc=pascal.mazon@6wind.com \
--cc=rahul.lakkireddy@chelsio.com \
--cc=rasesh.mody@cavium.com \
--cc=shepard.siegel@atomicrules.com \
--cc=shreyansh.jain@nxp.com \
--cc=skhare@vmware.com \
--cc=vido@cesnet.cz \
--cc=wenzhuo.lu@intel.com \
--cc=yuanhan.liu@linux.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).