From owner-freebsd-net@FreeBSD.ORG Sun Mar 1 21:50:09 2015 Return-Path: Delivered-To: freebsd-net@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 ABC983D6 for ; Sun, 1 Mar 2015 21:50:09 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [IPv6:2001:4f8:3:ffe0:406a:0:50:2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 8C272A02 for ; Sun, 1 Mar 2015 21:50:09 +0000 (UTC) Received: from phabric-backend.isc.freebsd.org (phabric-backend.isc.freebsd.org [127.0.1.5]) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9) with ESMTP id t21Lo9b9007192 for ; Sun, 1 Mar 2015 21:50:09 GMT (envelope-from root@phabric-backend.isc.freebsd.org) Received: (from root@localhost) by phabric-backend.isc.freebsd.org (8.14.9/8.14.9/Submit) id t21Lo9Yx007191; Sun, 1 Mar 2015 21:50:09 GMT (envelope-from root) Date: Sun, 1 Mar 2015 21:50:09 +0000 To: freebsd-net@freebsd.org From: "rpokala-panasas.com (Ravi Pokala)" Subject: [Differential] [Commented On] D1986: Teach lagg(4) to change MTU Message-ID: <803a84b435b46cef46d8af08a42e40e2@localhost.localdomain> X-Priority: 3 Thread-Topic: D1986: Teach lagg(4) to change MTU X-Herald-Rules: none X-Phabricator-To: X-Phabricator-To: X-Phabricator-Cc: X-Phabricator-Cc: In-Reply-To: References: Thread-Index: ODZhMzNlYThiYzMxOTgzYmRhMDE5M2Q2Yzk4IFTziZE= X-Phabricator-Sent-This-Message: Yes X-Mail-Transport-Agent: MetaMTA X-Auto-Response-Suppress: All X-Phabricator-Mail-Tags: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="utf-8" X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 01 Mar 2015 21:50:09 -0000 rpokala-panasas.com added a comment. >>! In D1986#4, @ae wrote: > Just a thought. Imagine two interfaces, one has maximum MTU 2200, another 1500. lagg0 has MTU 1400. > Two threads invokes changing MTU in the same time. One wants to change it to 2000, another - to 1500. > It is possible, that when both threads will finish its job, one interface will have MTU 1400, but another - 1500. > I mean, that such changes should be done exclusively without possibility of races in the ioctl code. Don't the calls to LAGG_RLOCK() / LAGG_RUNLOCK() prevent that by enforcing serialization? REVISION DETAIL https://reviews.freebsd.org/D1986 To: rpokala-panasas.com, rstone Cc: ae, freebsd-net