DPDK patches and discussions
 help / color / mirror / Atom feed
From: Shahaf Shuler <shahafs@mellanox.com>
To: Slava Ovsiienko <viacheslavo@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/mlx5: inherit master link settings for	representors
Date: Mon, 29 Apr 2019 08:54:30 +0000	[thread overview]
Message-ID: <AM0PR0502MB3795D78C9FF6D37F1A4587A6C3390@AM0PR0502MB3795.eurprd05.prod.outlook.com> (raw)
Message-ID: <20190429085430.xZKIlKZYhNPtf7twQf6qilVhC8kyANaN2SusP9m5i5c@z> (raw)
In-Reply-To: <1556338798-17768-1-git-send-email-viacheslavo@mellanox.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="UTF-8", Size: 819 bytes --]

Saturday, April 27, 2019 7:20 AM¸ Viacheslav Ovsiienko:
> Subject: [dpdk-dev] [PATCH] net/mlx5: inherit master link settings for
> representors
> 
> There are some physical link settings can be queried from Ethernet devices:
> link status, link speed, speed capabilities, duplex mode, etc. These setting do
> not make a lot of sense for representors due to missing physical link. The
> new kernel drivers dropped query for link settings for representors causing
> the ioctl call to fail. This patch adds some kind of emulation of link settings to
> PMD - representors inherit the link parameters from the master device. The
> actual link status (up/down) is retrieved from the representor device.
> 
> Signed-off-by: Viacheslav Ovsiienko <viacheslavo@mellanox.com>

Applied to next-net-mlx, thanks. 



  parent reply	other threads:[~2019-04-29  8:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-27  4:19 Viacheslav Ovsiienko
2019-04-27  4:19 ` Viacheslav Ovsiienko
2019-04-29  8:54 ` Shahaf Shuler [this message]
2019-04-29  8:54   ` Shahaf Shuler

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=AM0PR0502MB3795D78C9FF6D37F1A4587A6C3390@AM0PR0502MB3795.eurprd05.prod.outlook.com \
    --to=shahafs@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=viacheslavo@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 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).