From owner-freebsd-arch@FreeBSD.ORG Tue Dec 9 16:43:39 2014 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id EA5D6EE; Tue, 9 Dec 2014 16:43:39 +0000 (UTC) Received: from mail-pd0-x233.google.com (mail-pd0-x233.google.com [IPv6:2607:f8b0:400e:c02::233]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B39A0DC1; Tue, 9 Dec 2014 16:43:39 +0000 (UTC) Received: by mail-pd0-f179.google.com with SMTP id fp1so859067pdb.38 for ; Tue, 09 Dec 2014 08:43:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-type:content-disposition:in-reply-to :user-agent; bh=ANmtLqsgjdEoyRzZ37VqQRCa67IW6PlsQKLweH4ySS0=; b=i9wtSmOaC5Dq2l3y6yTFrRkzCr6g+eRaX9QP73SBnOqR06wTdjhmaEOD68KCjhoGH3 ql4PIw8+rlbftG4DbkjBt9abM0Ri+g1X6lV8YWueLD2FvsktxUbk/szfgA0P2jPA5CbH vj4LqWSAp0+H2qUzsjnkVpAT6pLE4Zb72PmCcL4+XRmhjlKWTMT+GFJ6FlXWI9NDvELY qVucCPJBia07imLm876+OF9TN43wmtU37eLrHCmgZLWhlbx6xhnCymY4g3QpnFHcaeSC zxRTkvYCjQ2H+QhcCiwoEpFSsX0yUVoiaWY4hAp3d2ceLtwujdqMQZ6Ij9a1S08EdW2z eDMw== X-Received: by 10.67.6.233 with SMTP id cx9mr7093600pad.110.1418143419194; Tue, 09 Dec 2014 08:43:39 -0800 (PST) Received: from ox ([24.6.44.228]) by mx.google.com with ESMTPSA id ug6sm1905915pbc.72.2014.12.09.08.43.37 for (version=TLSv1.2 cipher=RC4-SHA bits=128/128); Tue, 09 Dec 2014 08:43:38 -0800 (PST) Date: Tue, 9 Dec 2014 08:43:34 -0800 From: Navdeep Parhar To: Slawa Olhovchenkov Subject: Re: Adding new media types to if_media.h Message-ID: <20141209164334.GB3925@ox> Mail-Followup-To: Slawa Olhovchenkov , Eric Joyner , Adrian Chadd , Jack F Vogel , freebsd-arch@freebsd.org References: <20141209130412.GA81921@zxy.spb.ru> <20141209153539.GA3925@ox> <20141209163136.GA94186@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20141209163136.GA94186@zxy.spb.ru> User-Agent: Mutt/1.5.21 (2010-09-15) Cc: Adrian Chadd , Jack F Vogel , Eric Joyner , freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 09 Dec 2014 16:43:40 -0000 On Tue, Dec 09, 2014 at 08:31:36PM +0400, Slawa Olhovchenkov wrote: > On Tue, Dec 09, 2014 at 07:35:39AM -0800, Navdeep Parhar wrote: > > > On Tue, Dec 09, 2014 at 05:04:13PM +0400, Slawa Olhovchenkov wrote: > > > On Tue, Dec 09, 2014 at 01:05:27AM -0800, Eric Joyner wrote: > > > > > > > This is a continuation of a discussion from off the list: > > > > > > > > ixgbe needs to support devices with media types that aren't in if_media.h; > > > > for now those are 10GBaseKR, 10GBaseKX4, and 1000baseKX. Immediately, we're > > > > running into the issue that there is no room for all of these types under > > > > the IFM_ETHER category; there's only room for two more (and per John > > > > Baldwin, only one more if one of those two unused types is to be used for a > > > > reserved type). Long term, there are going to be tons of media types for > > > > future ethernet speeds like 25G, 50G, 100G, and etc, and ixl already > > > > supports media types that aren't in if_media.h, either. > > > > > > > > So, something needs to change. Does anyone have any thoughts on what should > > > > happen? I've thought of a few things, but I don't have an adequate grasp of > > > > what the pros/cons of each are: > > > > > > > > 1. Add a new media category (like IFM_ETHER) and change kernel code to > > > > treat it like the existing IFM_ETHER. This creates ~28 new media types we > > > > can use, but it may just be delaying the inevitable for a short time. > > > > > > > > 2. Extend media value from 32-bits to 64-bits. I don't have a good idea of > > > > what the consequences are of this on architectures that aren't amd64. > > > > > > > > 3. (Initially suggested by Adrian) would be to create a new media type > > > > struct (instead of using an int value) or adding an extra value to the > > > > existing ifmedia/ifmedia_entry struct for this. This sounds like the best > > > > solution to me, but I don't know how much effort it would take to implement > > > > -- does ifconfig need a lot of changing to handle this? > > > > > > > > Thoughts? Any previous discussions worth looking at? > > > > > > I think need support for media type and subtype, i.e.: > > > > > > cxl0: flags=8843 metric 0 mtu 1500 > > > options=ec07bb > > > ether 00:07:43:2c:af:10 > > > inet 37.220.36.28 netmask 0xffffff00 broadcast 37.220.36.255 > > > nd6 options=9 > > > media: Ethernet Unknown > > > status: active > > > > > > This is 40G SFP+ DAC. > > > > This doesn't look related to the discussion Eric started, but I'd like > > to point out that is not a reliable link -- "Unknown" media for > > cxgbe/cxl means the driver has no idea what kind of cable this is and is > > probably using incorrect settings that happen to work by accident (if > > this is a working setup). Please provide the output of "cxgbetool > > t5nex0 modinfo 0 raw" if you'd like to get to the bottom of this. > > Off-list or new thread is better since it has nothing to do with the > > stuff in if_media.h > > We already discussed about this setup. > I have next answer from install enginer: "and i'm quite sure it is a + > cable, Solid Optics is a highly respected cable/transceiver supplier. > they would not invoice us a + cable if it is not" > > Yes, I see in i2c 'Identifier Values' as '0Ch -- QSFP'. QDR (40Gbit). So this cable was sold to you as a QSFP+, identifies itself as QSFP (no plus), and seems to work even though it's not supposed to. > > This is a working setup. And this setup work at 40Gbit w/o errors. Ok, let's leave it at that then. Do keep an eye on things like checksum errors, link flaps, or any other signs of shaky signals on the wire. Regards, Navdeep > > I think driver idea about correct settings irrelevant to reported link > speed (reported speed may be need for automatic discovering by network > managemnt software, SNMP reporting and etc.) > _______________________________________________ > freebsd-arch@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arch > To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"