netdev - Re: [PATCH net-next 1/3] net: ethtool: add support for forward error correction modes

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:   Thu, 6 Jul 2017 18:38:31 -0700
From:   Dave Olson <olson@...ulusnetworks.com>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     Casey Leedom <leedom@...lsio.com>, Jakub Kicinski <kubakici@...pl>,
        Dustin Byford <dustin@...ulusnetworks.com>,
        Roopa Prabhu <roopa@...ulusnetworks.com>,
        "davem@...emloft.net" <davem@...emloft.net>,
        "linville@...driver.com" <linville@...driver.com>,
        "netdev@...r.kernel.org" <netdev@...r.kernel.org>,
        "vidya.chowdary@...il.com" <vidya.chowdary@...il.com>,
        Manoj Malviya <manojmalviya@...lsio.com>,
        Santosh Rastapur <santosh@...lsio.com>,
        "yuval.mintz@...gic.com" <yuval.mintz@...gic.com>,
        "odedw@...lanox.com" <odedw@...lanox.com>,
        "ariela@...lanox.com" <ariela@...lanox.com>,
        "galp@...lanox.com" <galp@...lanox.com>,
        "jeffrey.t.kirsher@...el.com" <jeffrey.t.kirsher@...el.com>
Subject: Re: [PATCH net-next 1/3] net: ethtool: add support for forward error
 correction modes

Andrew Lunn <andrew@...n.ch> wrote:
> And when we are talking about SFP modules, we are not talking about
> somebody who can just about boiling an egg and put bread in the
> toaster.
> 
> Anybody using these SFP modules knows a lot about networking, is a
> power user, and probably does not rely on plug and pray.

We have strong evidence that this is not the case with many system and
network admins...

Casey is right; the simplest mental model for end-users that can be
made to work reasonably is the best answer.

And from a user perspective, that means (to me, from watching customer
cases), keeping the customers settings if at all possible, and spitting
out warnings and errors when it can't work.

As Casey keeps saying, there is no model that will work in all (or even
most) of the interesting use cases, where cables can change with some
frequency, especially when there are lots of ports (as on switches).

Dave Olson
olson@...ulusnetworks.com