From owner-freebsd-hackers@FreeBSD.ORG Mon Feb 9 15:50:36 2015 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 78D3D77A for ; Mon, 9 Feb 2015 15:50:36 +0000 (UTC) Received: from na01-bl2-obe.outbound.protection.outlook.com (mail-bl2on0077.outbound.protection.outlook.com [65.55.169.77]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (Client CN "mail.protection.outlook.com", Issuer "MSIT Machine Auth CA 2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 19DE727E for ; Mon, 9 Feb 2015 15:50:34 +0000 (UTC) Received: from DM2PR0801MB0944.namprd08.prod.outlook.com (25.160.131.27) by DM2PR0801MB0942.namprd08.prod.outlook.com (25.160.131.25) with Microsoft SMTP Server (TLS) id 15.1.75.20; Mon, 9 Feb 2015 15:50:26 +0000 Received: from DM2PR0801MB0944.namprd08.prod.outlook.com ([25.160.131.27]) by DM2PR0801MB0944.namprd08.prod.outlook.com ([25.160.131.27]) with mapi id 15.01.0075.002; Mon, 9 Feb 2015 15:50:26 +0000 From: "Pokala, Ravi" To: Ryan Stone Subject: Re: Changing the MTU on a lagg device Thread-Topic: Changing the MTU on a lagg device Thread-Index: AQHQQn+0qPs6AFh2xkSO1q7r/b61upzkzTgAgAMn5QA= Date: Mon, 9 Feb 2015 15:50:25 +0000 Message-ID: References: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.4.7.141117 x-originating-ip: [24.6.178.251] authentication-results: gmail.com; dkim=none (message not signed) header.d=none; x-microsoft-antispam: BCL:0;PCL:0;RULEID:;SRVR:DM2PR0801MB0942; x-exchange-antispam-report-test: UriScan:; x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:; SRVR:DM2PR0801MB0942; x-forefront-prvs: 04825EA361 x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(377424004)(13464003)(92566002)(122556002)(110136001)(40100003)(2950100001)(86362001)(99286002)(83506001)(106116001)(2900100001)(46102003)(77156002)(62966003)(66066001)(76176999)(50986999)(2656002)(19580405001)(87936001)(102836002)(36756003)(19580395003)(54356999)(1411001); DIR:OUT; SFP:1101; SCL:1; SRVR:DM2PR0801MB0942; H:DM2PR0801MB0944.namprd08.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en; Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-OriginatorOrg: panasas.com X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Feb 2015 15:50:25.0622 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: acf01c9d-c699-42af-bdbb-44bf582e60b0 X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM2PR0801MB0942 Cc: "freebsd-hackers@freebsd.org" X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 09 Feb 2015 15:50:36 -0000 -----Original Message----- From: Ryan Stone Date: 2015-02-06, Friday at 23:38 To: Ravi Pokala Cc: "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