From owner-svn-src-all@freebsd.org Sun Aug 28 17:46:49 2016 Return-Path: Delivered-To: svn-src-all@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 E7C65B7888F; Sun, 28 Aug 2016 17:46:49 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98]) (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 A69DA2AAC; Sun, 28 Aug 2016 17:46:49 +0000 (UTC) (envelope-from slw@zxy.spb.ru) Received: from slw by zxy.spb.ru with local (Exim 4.86 (FreeBSD)) (envelope-from ) id 1be4AP-000Mpa-7I; Sun, 28 Aug 2016 20:46:45 +0300 Date: Sun, 28 Aug 2016 20:46:45 +0300 From: Slawa Olhovchenkov To: Adrian Chadd Cc: Bruce Simpson , Ryan Stone , "svn-src-head@freebsd.org" , Ryan Stone , "src-committers@freebsd.org" , "svn-src-all@freebsd.org" Subject: Re: svn commit: r304436 - in head: . sys/netinet Message-ID: <20160828174645.GO88122@zxy.spb.ru> References: <20160826151324.GF88122@zxy.spb.ru> <20160826213613.GH88122@zxy.spb.ru> <20160826220255.GI88122@zxy.spb.ru> <20160827004617.GJ88122@zxy.spb.ru> <20160828133012.GN88122@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Aug 2016 17:46:50 -0000 On Sun, Aug 28, 2016 at 10:20:08AM -0700, Adrian Chadd wrote: Hi, thanks for answer! > Hi, > > There are some no brainers here so far(tm): > > working from the bottom up: > > * yeah, the ixgbe locking is a bit silly. Kip's work with iflib and > converting ixgbe to use that instead of its own locking for managing > things should remove the bottom two locks I think no MFC to stbale/10 planed? > * the rtalloc1_fib thing - that's odd, because it shouldn't be > contending there unless there's some temporary redirect that's been > learnt. What's the routing table look like on your machine? I Remember # netstat -rn Routing tables Internet: Destination Gateway Flags Netif Expire default 37.220.36.1 UGS lagg0 37.220.36.0/24 link#6 U lagg0 37.220.36.11 link#6 UHS lo0 127.0.0.1 link#5 UH lo0 Internet6: Destination Gateway Flags Netif Expire ::/96 ::1 UGRS lo0 ::1 link#5 UH lo0 ::ffff:0.0.0.0/96 ::1 UGRS lo0 fe80::/10 ::1 UGRS lo0 fe80::%lo0/64 link#5 U lo0 fe80::1%lo0 link#5 UHS lo0 ff01::%lo0/32 ::1 U lo0 ff02::/16 ::1 UGRS lo0 ff02::%lo0/32 ::1 U lo0 > investigating the rtentry reference counting a while ago and concluded > that .. it's terrible, and one specific corner case was checking for > routes from redirects. I'll look at my notes again and see what I > find. > > kernel`vm_object_madvise+0x39e > kernel`vm_map_madvise+0x3bb > kernel`sys_madvise+0x82 > kernel`amd64_syscall+0x40f > kernel`0xffffffff806c8bbb > 97389657 > > .. something's doing frequent madvise calls, which may be causing some In any case, this is create load on different CPU cores. > hilarity between threads. What's the server? nginx? yes > Then the rest of the big entries are just a combination of rtentry > locking, tcp timer locking, zfs locking and madvise locking. There's > some sowakeup locking there as well, from the socket producer/consumer > locking. > > > > > -adrian