From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] ethdev link speed
Date: Wed, 8 Apr 2020 00:26:35 +0200 [thread overview]
Message-ID: <20200407222637.55289-1-thomas@monjalon.net> (raw)
In-Reply-To: <98CBD80474FA8B44BF855DF32C47DC35C60F3C@smartserver.smartshare.dk>
Following 2 discussions about link speed,
here is an API update and a small clean-up.
Morten's proposal:
http://inbox.dpdk.org/dev/4957996.Zugxlq0yvN@xps/
Recent Ivan's virtio patch assuming the same API update:
http://inbox.dpdk.org/dev/20200406085855.25773-6-i.dyukov@samsung.com/
Benoit's proposal to return mlx5 link status even without speed info:
http://inbox.dpdk.org/dev/20200327172449.6514-1-bganne@cisco.com/
Thomas Monjalon (2):
ethdev: deduplicate functions to get link infos
ethdev: allow unknown link speed
lib/librte_ethdev/rte_ethdev.c | 52 ++++++++++++++--------------------
lib/librte_ethdev/rte_ethdev.h | 20 ++++++-------
2 files changed, 32 insertions(+), 40 deletions(-)
--
2.26.0
next prev parent reply other threads:[~2020-04-07 22:26 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 9:33 [dpdk-dev] [RFC] ethdev: use special speed for virtual Ethernet devices Morten Brørup
2020-04-01 9:53 ` Thomas Monjalon
2020-04-01 10:03 ` Benoit Ganne (bganne)
2020-04-01 10:06 ` [dpdk-dev] [RFC] ethdev: use special speed for virtual Ethernetdevices Morten Brørup
2020-04-02 12:54 ` Ivan Dyukov
2020-04-02 13:50 ` Morten Brørup
2020-04-02 15:29 ` Stephen Hemminger
2020-04-02 20:41 ` Ivan Dyukov
2020-04-02 20:58 ` Thomas Monjalon
2020-04-03 8:05 ` Ivan Dyukov
2020-04-03 9:45 ` Morten Brørup
2020-04-03 11:01 ` Thomas Monjalon
2020-04-07 22:26 ` Thomas Monjalon [this message]
2020-04-07 22:26 ` [dpdk-dev] [PATCH 1/2] ethdev: deduplicate functions to get link infos Thomas Monjalon
2020-04-08 5:21 ` Asaf Penso
2020-04-08 12:49 ` Thomas Monjalon
2020-04-13 14:14 ` Andrew Rybchenko
2020-04-07 22:26 ` [dpdk-dev] [PATCH 2/2] ethdev: allow unknown link speed Thomas Monjalon
2020-04-08 5:39 ` Jerin Jacob
2020-04-10 10:53 ` Morten Brørup
2020-04-13 14:26 ` Andrew Rybchenko
2020-04-16 13:42 ` Ferruh Yigit
2020-04-26 11:44 ` Matan Azrad
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=20200407222637.55289-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@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).