From owner-freebsd-net@freebsd.org  Fri Jan 20 18:36:47 2017
Return-Path: <owner-freebsd-net@freebsd.org>
Delivered-To: freebsd-net@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id BCC2CCB9206
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Fri, 20 Jan 2017 18:36:47 +0000 (UTC)
 (envelope-from wollman@hergotha.csail.mit.edu)
Received: from hergotha.csail.mit.edu
 (wollman-1-pt.tunnel.tserv4.nyc4.ipv6.he.net [IPv6:2001:470:1f06:ccb::2])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 86B7E1E73
 for <freebsd-net@freebsd.org>; Fri, 20 Jan 2017 18:36:47 +0000 (UTC)
 (envelope-from wollman@hergotha.csail.mit.edu)
Received: from hergotha.csail.mit.edu (localhost [127.0.0.1])
 by hergotha.csail.mit.edu (8.15.2/8.15.2) with ESMTP id v0KIajqp014328;
 Fri, 20 Jan 2017 13:36:45 -0500 (EST)
 (envelope-from wollman@hergotha.csail.mit.edu)
Received: (from wollman@localhost)
 by hergotha.csail.mit.edu (8.15.2/8.14.4/Submit) id v0KIailL014327;
 Fri, 20 Jan 2017 13:36:44 -0500 (EST) (envelope-from wollman)
Date: Fri, 20 Jan 2017 13:36:44 -0500 (EST)
From: Garrett Wollman <wollman@hergotha.csail.mit.edu>
Message-Id: <201701201836.v0KIailL014327@hergotha.csail.mit.edu>
To: gallatin@netflix.com
Subject: Re: RFC: ethctl
In-Reply-To: <c21ec3d9-a539-6c7d-4bd3-6413e7149b2b@netflix.com>
References: <c21ec3d9-a539-6c7d-4bd3-6413e7149b2b@netflix.com>
 <CAK7dMtCSRu6L67A46FU0eYqJ9=zGdyJPvBXLkL7gKbh=SbZ6cQ@mail.gmail.com>
Organization: none
Cc: freebsd-net@freebsd.org
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.1
 (hergotha.csail.mit.edu [127.0.0.1]); Fri, 20 Jan 2017 13:36:45 -0500 (EST)
X-Spam-Status: No, score=-1.0 required=5.0 tests=ALL_TRUSTED
 autolearn=disabled version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on
 hergotha.csail.mit.edu
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2017 18:36:47 -0000

In article <c21ec3d9-a539-6c7d-4bd3-6413e7149b2b@netflix.com> you write:
>Eg, I don't see why we need another tool for some of this missing
>"ethtool" functionality; it seems like most of it would naturally fit
>into ifconfig.

>From the end-user perspective, I agree with Drew.  Most of this stuff
should just be part of ifconfig.

>As to other features, like writing firmware images and/or reading
>dumping eeprom -- these were never a natural fit for us.

And I can't say that I've ever wanted to do this.  Most of the
machines we buy these days are Dells, and Dell USC takes care of all
the firmware updates.  Having a not-really-generic firmware
programming interface that only works for network interfaces seems
like very limited value.  I wouldn't object to it, but I doubt I'd
ever use it, and I expect most vendors will want to keep tighter
control over applying firmware updates.

-GAWollman