From owner-freebsd-net@freebsd.org Fri May 27 17:32:53 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 C2647B4C4C4 for ; Fri, 27 May 2016 17:32:53 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: from mail-io0-x243.google.com (mail-io0-x243.google.com [IPv6:2607:f8b0:4001:c06::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 8A46514C5; Fri, 27 May 2016 17:32:53 +0000 (UTC) (envelope-from dmarquess@gmail.com) Received: by mail-io0-x243.google.com with SMTP id m17so5719601ioi.3; Fri, 27 May 2016 10:32:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to; bh=XYmAnMlzlluFwfWX30e242sZ3H2tVoMTiIce7CW5Ln8=; b=RMv309SxecGp/e1vlrT5OlA/v88umzhnTCqbw3mQafh0bTOxfWCNxH/AiYFDaEoU9W pH/6PwtWCssKcdq8tAAsJ4+SuwStQmCmkmCRL+zfpFTFaRK0T6njaGJ/2ulm1Po/FdW5 /o0HUJ4FJQcQtnrmtwO+iNEx+QGzf+nELkQ8eTmUOBT+5JmSQprTmVdBDsJYCRcQLFXg fZ4kxL1qEG0uq2m4lTvRAhTF1Y3dGbAczUgxiZtf8v9ze7heYdn6+1VtNEqm68gM7gB3 pbrTgaTgo6f4BFtIxqEMONjNqUbd+LRroqZF69mb6NEl+zgTS9oJVWfmxF9lXOsRL5b4 qbqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to; bh=XYmAnMlzlluFwfWX30e242sZ3H2tVoMTiIce7CW5Ln8=; b=IiFnEsZ7oIPjwPnUCPaulwTHw+KcK++JDHxTpwP7cJj/HKbm8FI6EK03hO4Gd6i16M 2QYsPRSpD8fHD8TV+gax9UYOX9Lb/YnVMZrFPgCx9RwEOQF+lbk8FCz7u1WuKSrQF4jD f1KGDvdrXjNdrWsnUorgfmkFQ9oHAP0QSPrGHCzK9lCrl9ZGQS0guO51YtZN3bPAz5m5 kMJx33kMj5Elm8r2S1+VUv9bLhu2S64wzT+qRYFlGzTy4JV1jpPWwfsQBOVi2Y3I0BV5 tdb+Yc2M4gE+Tslq5OpMc+skqOV51PG4NeuaczU6a+t8VyeE3h6mJjgbHuzwyAlZdI1l 9Aow== X-Gm-Message-State: ALyK8tJ4KbLYp1EaIpgKoIof9TT43z+EI3tk5JwBMFBZG6zDfkADxaVvoPh78ee8G99GHJ1nvZHsXPsIdbz63w== MIME-Version: 1.0 X-Received: by 10.107.46.158 with SMTP id u30mr14620116iou.162.1464370372818; Fri, 27 May 2016 10:32:52 -0700 (PDT) Received: by 10.107.148.69 with HTTP; Fri, 27 May 2016 10:32:52 -0700 (PDT) In-Reply-To: <20160527072951.GC10148@ox> References: <201605270457.u4R4vYqu018911@hergotha.csail.mit.edu> <20160527063731.GB10148@ox> <20160527072951.GC10148@ox> Date: Fri, 27 May 2016 12:32:52 -0500 Message-ID: Subject: Re: Changing MTU on cxgbe From: Dustin Marquess To: "K. Macy" , Garrett Wollman , "dmarquess@gmail.com" , "freebsd-net@freebsd.org" Content-Type: text/plain; charset=UTF-8 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 17:32:53 -0000 Okay, so ya, I'm stupid. The MTU won't change w/ ifconfig on the command line because of the lagg/bridge. The real issue seems to be ifconfig ordering, eg: ifconfig_cxgbe0="mtu 9000 toe4 toe6 up" Works ifconfig_cxgbe0="toe4 toe6 mtu 9000 up" Does NOT. So that's what was biting me in the butt. Sorry for the spam guys! -Dustin On Fri, May 27, 2016 at 2:29 AM, Navdeep Parhar wrote: > On Fri, May 27, 2016 at 12:23:02AM -0700, K. Macy wrote: >> On Thursday, May 26, 2016, Navdeep Parhar wrote: >> >> > On Fri, May 27, 2016 at 12:57:34AM -0400, Garrett Wollman wrote: >> > > In article < >> > CAJpsHY4vF5Ky6GuAusLOOROgiQuyD2CcRmVxu8x3cArQRZxcbg@mail.gmail.com >> > > 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 >> > >> > This is not correct. You can change the MTU of a cxgbe/cxl interface at >> > any time (whether it's up or down, passing traffic or idle, etc.). >> >> >> For some reason the stack needs init to be called when the MTU is changed >> for it to actually change the size of the packets passed to the driver. At >> least cxgb does not do that. I'm not at my computer right now, but cxgbe >> may be the same. If that's the case just up / down the interface. It _will_ >> take effect without that if it's passed at module load. > > The problem that was reported was that the ioctl that sets the MTU > failed, not that the ioctl succeeded but the MTU change did not take > effect. > > Regards, > Navdeep