From owner-freebsd-net@freebsd.org Fri May 27 04:57:37 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 0823EB465C2 for ; Fri, 27 May 2016 04:57:37 +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 with cipher DHE-RSA-CAMELLIA256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id B328816BA for ; Fri, 27 May 2016 04:57:36 +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.14.9/8.14.9) with ESMTP id u4R4vYiZ018912; Fri, 27 May 2016 00:57:34 -0400 (EDT) (envelope-from wollman@hergotha.csail.mit.edu) Received: (from wollman@localhost) by hergotha.csail.mit.edu (8.14.9/8.14.4/Submit) id u4R4vYqu018911; Fri, 27 May 2016 00:57:34 -0400 (EDT) (envelope-from wollman) Date: Fri, 27 May 2016 00:57:34 -0400 (EDT) From: Garrett Wollman Message-Id: <201605270457.u4R4vYqu018911@hergotha.csail.mit.edu> To: dmarquess@gmail.com Subject: Re: Changing MTU on cxgbe References: Organization: none Cc: freebsd-net@freebsd.org X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (hergotha.csail.mit.edu [127.0.0.1]); Fri, 27 May 2016 00:57:34 -0400 (EDT) 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.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 04:57:37 -0000 In article you write: ># ifconfig -m cxgbe0 >cxgbe0: flags=8943 ># ifconfig cxgbe0 mtu 9000 >ifconfig: ioctl SIOCSIFMTU (set mtu): Invalid argument I believe this device, like many others, does not allow the MTU (or actually the MRU) to be changed once the receive ring has been set up You may be able to do it if you down the interface first, or you may have to do it at boot time before anything else (and in particular before the interface is marked "up" for the first time). -GAWollman