From owner-svn-src-head@freebsd.org Fri Jun 2 10:30:41 2017 Return-Path: Delivered-To: svn-src-head@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 A2A4ABF4606; Fri, 2 Jun 2017 10:30:41 +0000 (UTC) (envelope-from prvs=319e99cc0=roger.pau@citrix.com) Received: from SMTP.EU.CITRIX.COM (smtp.ctxuk.citrix.com [185.25.65.24]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (Client CN "mail.citrix.com", Issuer "DigiCert SHA2 Secure Server CA" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 901418282E; Fri, 2 Jun 2017 10:30:39 +0000 (UTC) (envelope-from prvs=319e99cc0=roger.pau@citrix.com) X-IronPort-AV: E=Sophos;i="5.39,284,1493683200"; d="scan'208";a="47113062" Date: Fri, 2 Jun 2017 11:29:22 +0100 From: Roger Pau =?iso-8859-1?Q?Monn=E9?= To: Colin Percival CC: , , Subject: Re: svn commit: r319491 - head/sys/dev/xen/netfront Message-ID: <20170602102922.stlu47ceumggu6o7@dhcp-3-128.uk.xensource.com> References: <201706020703.v5273V5A085287@repo.freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline In-Reply-To: <201706020703.v5273V5A085287@repo.freebsd.org> User-Agent: NeoMutt/20170428 (1.8.2) X-ClientProxiedBy: AMSPEX02CAS02.citrite.net (10.69.22.113) To AMSPEX02CL02.citrite.net (10.69.22.126) X-BeenThere: svn-src-head@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SVN commit messages for the src tree for head/-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Jun 2017 10:30:41 -0000 On Fri, Jun 02, 2017 at 07:03:31AM +0000, Colin Percival wrote: > Author: cperciva > Date: Fri Jun 2 07:03:31 2017 > New Revision: 319491 > URL: https://svnweb.freebsd.org/changeset/base/319491 > > Log: > Skip setting the MTU in the netfront driver (xn# devices) if the new MTU > is the same as the old MTU. In particular, on Amazon EC2 "T2" instances > without this change, the network interface is reinitialized every 30 > minutes due to the MTU being (re)set when a new DHCP lease is obtained, > causing packets to be dropped, along with annoying syslog messages about > the link state changing. > > As a side note, the behaviour this commit fixes was responsible for > exposing the locking problems fixed via r318523 and r318631. > > Maintainers of other network interface drivers may wish to consider making > the corresponding change; the handling of SIOCSIFMTU does not seem to > exhibit a great deal of consistency between drivers. Is there any reason this check (ifp->if_mtu == ifr->ifr_mtu) is not done at a higher level for all the drivers? It seems pointless to add this chunk everywhere. Roger.