Date: Mon, 9 Feb 2015 15:50:25 +0000 From: "Pokala, Ravi" <rpokala@panasas.com> To: Ryan Stone <rysto32@gmail.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: Changing the MTU on a lagg device Message-ID: <D0FE1707.12C783%rpokala@panasas.com> In-Reply-To: <CAFMmRNwx=-ZzVLLj8v3jHnHcV_ziaXb87QTEO3FvkwC5kEOp1g@mail.gmail.com> References: <D0FABB8B.12C626%rpokala@panasas.com> <CAFMmRNwx=-ZzVLLj8v3jHnHcV_ziaXb87QTEO3FvkwC5kEOp1g@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
-----Original Message----- From: Ryan Stone <rysto32@gmail.com> Date: 2015-02-06, Friday at 23:38 To: Ravi Pokala <rpokala@panasas.com> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: Changing the MTU on a lagg device >I have a similar patch internally. As best that I can tell, the author >of the code didn't want to go to the effort of implementing the error >cases on the MTU change, and thought that it was better to explicitly >error out if somebody tried to change the MTU rather than causing random >unexpected behaviour. You can put me (rstone@) as a reviewer in >phabricator if you need your patch reviewed. I'm not sure I have phabricator access. If / when it comes to that, I'll be sure to put you down as a reviewer. Thanks Ryan! -Ravi
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D0FE1707.12C783%rpokala>