Date: Thu, 26 May 2016 23:37:31 -0700 From: Navdeep Parhar <nparhar@gmail.com> To: Garrett Wollman <wollman@hergotha.csail.mit.edu> Cc: dmarquess@gmail.com, freebsd-net@freebsd.org Subject: Re: Changing MTU on cxgbe Message-ID: <20160527063731.GB10148@ox> In-Reply-To: <201605270457.u4R4vYqu018911@hergotha.csail.mit.edu> References: <CAJpsHY4vF5Ky6GuAusLOOROgiQuyD2CcRmVxu8x3cArQRZxcbg@mail.gmail.com> <201605270457.u4R4vYqu018911@hergotha.csail.mit.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> > > ># 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.). Regards, Navdeep
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20160527063731.GB10148>