From owner-freebsd-net@freebsd.org Sat Jan 21 18:17:21 2017 Return-Path: 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 B07CBCBBB89 for ; Sat, 21 Jan 2017 18:17:21 +0000 (UTC) (envelope-from hoomanfazaeli@gmail.com) Received: from mail-wm0-x243.google.com (mail-wm0-x243.google.com [IPv6:2a00:1450:400c:c09::243]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 45690EFF for ; Sat, 21 Jan 2017 18:17:21 +0000 (UTC) (envelope-from hoomanfazaeli@gmail.com) Received: by mail-wm0-x243.google.com with SMTP id r126so15037969wmr.3 for ; Sat, 21 Jan 2017 10:17:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-transfer-encoding; bh=wWkJ0qmJrYj0vjwqg4L1LJTyyPhjZGqq0p0Rks8nF6Q=; b=t8GsoT6u6+JvYSUpX1iuL3DWl93gSIQviTi1EI71bWR4wfSKl+W97l7cKNuxNJmIZI 3ClInMqZS4tqKwPmwHmt9FW1ceYUVRL2DBR+7FD6xHb4fUsgCrIjZHKw4OkNWnGXSfhc 4DzUAWhW/oh90IPMVJGZ23dVuDaV9wYU57N6aLu/NqVdU5O3tvm96svhp6k6mCR2/ur0 zf6Ymqb7iZaw6gKoL6sB7C3WZU+OcyX9+EAMYoPbHhLKtiK6/4F3R1iUgLjagCVjWeZd 5OMVxPEypgp0uw0cxh4vz5Tu94zet7AGHUQmtNUaF+DWT0Wfy0jB3lkYdsQrDkGGRWRU qy3A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :cc:subject:references:in-reply-to:content-transfer-encoding; bh=wWkJ0qmJrYj0vjwqg4L1LJTyyPhjZGqq0p0Rks8nF6Q=; b=tApGYvGjC+hOI54VTf47ijDjZplXuKDNKIksrjjw4kTw8qTmeLX4vfy/XzIEe7b7CH /it840px0EhXuLaGcobZVclsT8cXYZTwC7dsHDAAuaaPSigyn+KN1dQ8+je+t81xt0PU /ekjFgcG3WqaoYQRJf4+Gn3QT0Mpx7UIwef9ugtn+sjlQKbDLUMOaPd7ddEg5bkw2WKG nqt0FXjjYu4dFBeTvFR/6IsqIVBL+U+klr3tycYlAyzu6KrzvPzvpUngR8z5pKTQXJAW oXzwymyujiVVKgBwVbl8fNMzOkQLIPqY0eVpxXBktuz2obQD0eqlLPrIe3BVOQ7Lu1PD LG1Q== X-Gm-Message-State: AIkVDXKswzApUH/omUJWLLlOEMIColcwFiRVYjEfiPOCgxEi6vGB3g3+2tRqdT0k5ShOmw== X-Received: by 10.223.134.218 with SMTP id 26mr16317702wry.104.1485022639384; Sat, 21 Jan 2017 10:17:19 -0800 (PST) Received: from [192.168.2.30] ([2.190.191.90]) by smtp.googlemail.com with ESMTPSA id k11sm11953667wmb.18.2017.01.21.10.17.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 21 Jan 2017 10:17:18 -0800 (PST) Message-ID: <5883A5A7.2050503@gmail.com> Date: Sat, 21 Jan 2017 21:47:11 +0330 From: Hooman Fazaeli User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3 MIME-Version: 1.0 To: Kevin Bowling CC: freebsd-net@freebsd.org Subject: Re: RFC: ethctl References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2017 18:17:21 -0000 On 2017-01-20 07:28, Kevin Bowling wrote: > Greetings, > > I'm casting a wide net in cc, try to keep the noise minimal but we need > some input from a variety of HW vendors. > > I have heard from several vendors the need for a NIC configuration tool. > Chelsio ships a cxgb/cxgbetool in FreeBSD as one example. There is > precedence for some nod toward a basic unified tool in Linux ethtool. > > From your perspective, > 1) What are the common requirements? > 2) What are specialized requirements? For instance as a full TCP offload > card Chelsio needs things others wont > 3) What should it _not_ do? Several of you have experience doing Ethernet > driver dev on many platforms so we should attempt to avoid repeating past > design mistakes. > > I expect we can achieve some level of inversion so the device specific code > can live close to the driver and plug into the ethctl framework. It should > be general enough to add completely new top level commands, so vendors can > implement HW specific features. On the other hand, we should attempt to > hook into common core for features every NIC provides, with a focus on > iflib. > > I will fund Matt Macy to do the overall design and implementation. > > Regards, > Kevin Bowling, on behalf of Limelight Networks for this effort > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" I always wished FreeBSD had a device-independent tool/API which could be used to query a device's Ethernet specific statisticssuch ascollisions, symbol/sequence/CRC/alignment errors, missed packets, giants & runts,link state IRQs, mbuf allocation fails, ... which are valuable for monitoring and diagnostics (BTW, I am aware that some drivers export a few counters via sysctl interface, but what I am talking about is a standardized set of counters available for _all_ Ethernet devices). -- Best regards Hooman Fazaeli