From owner-freebsd-net@freebsd.org Fri May 27 06:35:32 2016 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 74DA3B4CD0B for ; Fri, 27 May 2016 06:35:32 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::235]) (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 4692C1D8D for ; Fri, 27 May 2016 06:35:32 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: by mail-pf0-x235.google.com with SMTP id b124so38778631pfb.0 for ; Thu, 26 May 2016 23:35:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:date:from:to:cc:subject:message-id:mail-followup-to :references:mime-version:content-disposition:in-reply-to:user-agent; bh=7866RGmquE2klJ++nINFni6n2hKxsPfba6ek0612MWA=; b=Xp0/38r5nLPPxS4gLn8bmZXxakDRCU4ynnDnM4gEpwfSBL325h9YgHmVjUIayGqXT7 ljaENAv0KL+SOGWSTBzgVr9/pgpMnGNx5RgtkwQz9P4FvcXlOGenS6lRQU+R76NG4OAp pbqS9+0BhbVTxxdqY2yj1BUj/d/Iushk5n7gh0FiBVfMnX8K9cEUTHOnn9T4LhtnC8qw 9YYrM0X3Tby0uSz440cVnPRkD5XjRv3Xmx993ovp/5x2tp+ueWbViuEbhY9OZtsK2gqO UR0FfWNtX3xyWMOSBqbokfvC1tK/22A7kvlj9/8Hq2z/Gx7dB6twhFMp3ZrgbvCiEhP5 Uhsw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=7866RGmquE2klJ++nINFni6n2hKxsPfba6ek0612MWA=; b=d/3785ZawCmX7hsPNUztDwRUmXe6ZdSfJ9T2BlurSdsxoKnBPBDny7svNm8QrZRV33 JPXqPgKUPhpcBk0apsamCHD8NNXL8ukQPLVLj2rBu7xewnzsRkf5yRlDp1U9+iH/zJ30 NP6ct39a+CkZi9+zES+ZWq4TXLl9moYfInF+uddHa2jtRAceIhbzMkr6AtCAjcF3cOll zd0SxzJwu+prh6p8BWZDVuaHjQ5SFmVNKqZq5WK3pSfl8IY/nT80tRRSHVYXP+Ukxdad r8kWFqdhMvCx2b3Roj8QxjFM4iEyPM8YEBmeRuIUFOxYqZdW+pSn4oJ207avlrxgkVVY j+LA== X-Gm-Message-State: ALyK8tICctpEiWdeW1q0guyHouM8JuMFThNnrL/ho2vcZsI/3NE8IhRPWwep3iBfHlEH0w== X-Received: by 10.98.23.18 with SMTP id 18mr20037805pfx.96.1464330931640; Thu, 26 May 2016 23:35:31 -0700 (PDT) Received: from ox ([2601:641:c180:c600:29bb:647c:963d:7705]) by smtp.gmail.com with ESMTPSA id 7sm10625626pfn.30.2016.05.26.23.35.30 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 26 May 2016 23:35:30 -0700 (PDT) Sender: Navdeep Parhar Date: Thu, 26 May 2016 23:35:22 -0700 From: Navdeep Parhar To: Dustin Marquess Cc: freebsd-net@freebsd.org Subject: Re: Changing MTU on cxgbe Message-ID: <20160527063522.GA10148@ox> Mail-Followup-To: Dustin Marquess , freebsd-net@freebsd.org References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 27 May 2016 06:35:32 -0000 On Thu, May 26, 2016 at 11:52:45PM -0500, Dustin Marquess wrote: > After my many issues with ixgbe & ixv, I ended up removing the Intel > X520s with Chelsio T420-CR and the Intel X710s with Chelsio T520-CR. > So far so good, except I can't seem to change the MTU away from 1500. > In fact, ifconfig can't seem to change the mtu at all. On -CURRENT as > of yesterday: > > # ifconfig -m cxgbe0 > cxgbe0: flags=8943 > metric 0 mtu 1500 > options=ec07bb > capabilities=ecc7bb > ether 00:07:43:11:2b:80 > nd6 options=29 > media: Ethernet 10Gbase-Twinax > status: active > supported media: > media 10Gbase-Twinax mediaopt full-duplex > > # ifconfig cxgbe0 mtu 9000 > ifconfig: ioctl SIOCSIFMTU (set mtu): Invalid argument > > # ifconfig cxgbe0 mtu 1500 > ifconfig: ioctl SIOCSIFMTU (set mtu): Invalid argument > > Any ideas? It should have worked. I tried just now on a system running -CURRENT as of today (r300785) and didn't encounter any problems. # ifconfig cxl0 up # ifconfig cxl0 mtu 500 # ifconfig cxl0 mtu 3333 # ifconfig cxl0 mtu 7992 ... Is the cxgbe/cxl ifnet part of a lagg or bridge or something like that? Run this while you try the ifconfig and see what ioctls are failing with EINVAL. You may have to do a "kldload dtraceall" before this. # dtrace -n 'fbt::*_ioctl:return /arg1 == 22/ {}' > Also, the Chelsios don't seem to use iovctl to do SR-IOV like the > Intels did (I'm using bhyve). I assume that's what the > hw.cxgbe.num_vis loader setting is for? num_vis does create multiple autonomous ifnets that share the same physical port but it doesn't involve SR-IOV. Regards, Navdeep