From owner-svn-src-all@freebsd.org Sun Aug 28 17:20:11 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 637F5B78206; Sun, 28 Aug 2016 17:20:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-it0-x22d.google.com (mail-it0-x22d.google.com [IPv6:2607:f8b0:4001:c0b::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 28247D70; Sun, 28 Aug 2016 17:20:11 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: by mail-it0-x22d.google.com with SMTP id g62so67411427ith.1; Sun, 28 Aug 2016 10:20:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=n6vxE3EGmWl2AHMdOJ7KqDYbIo4l/jFhpN/tw2zYljo=; b=gqPocXAP8Foo8wbL5KYakOuhow7G8RVpTfAeNJcPKXImCzicdEiTTCUny8pCYO3VO4 bAsQPkNOrW/FePg5viZEq3SRHRdGnJ6QgRtTavYQzQJTSdf1GpmpC5xmix+GBnSlzXQI EK+c9wkAW3iNWuyLS61UyoHfh3PlGzwzNGkXSeEGs/MJGfDNZVu+Wth1c7ztxvXuDULt qxX4L70DCom6OiEo7TlHaBX16ypcC8RiBhS4vzwH7TZET0lVhRPQ/agHFc08+M00EimQ S4S7O18zDeIFCt5RmtE1G3kZFBj8oBywJ6/ydLE6bZccYcl6q4WApzDnusgM+ecPksvO l7MQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=n6vxE3EGmWl2AHMdOJ7KqDYbIo4l/jFhpN/tw2zYljo=; b=kkWWI0bkavUv3FFoyVlJHz7Ar3Y+wboIcnXBFStS+QcHOp+t9WrtW2AgQI1X9pb/VN 61OzlySupg5Dy0kJo50qr6RJYlVjqjfi2gjdAhL3BG43ILvrnykfJpnXnLxK898cHLND SbjvVbjh1ImkQOz8RFdG0deNBfaJG7h6wY3sko71WEn5iStpMvu/NhWTF+ZCKsL/uRp1 5+CyXwG9wJ0v2yPtaiDDZoJNX5ZlEPm1c3sryjTkBL3keQlhaE04LalM51SnZCjdJfBZ J7PrGwaujMoikLYO1eduX7str1EF+33R0qDiD28jVkJ+KhBcuxxd8D39hRK/PRsVgbYA nU9A== X-Gm-Message-State: AE9vXwPJDXHlqDMzO/4A7iBwZKQ+0BLLxSq/zyDSAG0nB1ocwhL4MVdIPtTauyEARtB4l+sbi0YHczILyBmD4g== X-Received: by 10.36.73.195 with SMTP id e64mr8962239itd.80.1472404810395; Sun, 28 Aug 2016 10:20:10 -0700 (PDT) MIME-Version: 1.0 Sender: adrian.chadd@gmail.com Received: by 10.36.141.129 with HTTP; Sun, 28 Aug 2016 10:20:08 -0700 (PDT) In-Reply-To: <20160828133012.GN88122@zxy.spb.ru> References: <20160826144926.GE88122@zxy.spb.ru> <3dba1b70-54cc-0bb1-5cc8-8c56cd750bec@fastmail.net> <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> From: Adrian Chadd Date: Sun, 28 Aug 2016 10:20:08 -0700 X-Google-Sender-Auth: N5abUsHrJ-vhww41PPUoPmq2S5g Message-ID: Subject: Re: svn commit: r304436 - in head: . sys/netinet To: Slawa Olhovchenkov Cc: Bruce Simpson , Ryan Stone , "svn-src-head@freebsd.org" , Ryan Stone , "src-committers@freebsd.org" , "svn-src-all@freebsd.org" Content-Type: text/plain; charset=UTF-8 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:20:11 -0000 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 * 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 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 hilarity between threads. What's the server? nginx? 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