[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <MWHPR12MB1600C9C8528A929DD0404943C85B0@MWHPR12MB1600.namprd12.prod.outlook.com>
Date: Wed, 15 Feb 2017 17:38:07 +0000
From: Casey Leedom <leedom@...lsio.com>
To: Vidya Sagar Ravipati <vidya@...ulusnetworks.com>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
"linville@...driver.com" <linville@...driver.com>,
"jeffrey.t.kirsher@...el.com" <jeffrey.t.kirsher@...el.com>,
"davem@...emloft.net" <davem@...emloft.net>
CC: "roopa@...ulusnetworks.com" <roopa@...ulusnetworks.com>,
"dustin@...ulusnetworks.com" <dustin@...ulusnetworks.com>,
"odedw@...lanox.com" <odedw@...lanox.com>,
"ariela@...lanox.com" <ariela@...lanox.com>,
"Yuval.Mintz@...gic.com" <Yuval.Mintz@...gic.com>,
"galp@...lanox.com" <galp@...lanox.com>,
"vidya.chowdary@...il.com" <vidya.chowdary@...il.com>
Subject: Re: [RFC PATCH v2] net: ethtool: add support for forward error
correction modes
Vidya and I have been in communication on how to support Forward Error Correction Management on Links. My own thoughts are that we should consider using the new Get/Set Link Ksettiongs API because FEC is a low-level Link parameter which is either negotiated at the same time as Link Speed if Auto-Negotiation is in use, or must be set identically on both Link Peers is AN is not in use. I'm not convinced that FEC Management should use a separate ethtool/Kernel Driver API ala Pause Frame settings.
I'm hoping to meet with Vidya and his collaborators at Cumulus Networks in the very near term to hash these issues out.
Casey
Powered by blists - more mailing lists