From owner-freebsd-stable@freebsd.org Wed Oct 12 17:32:20 2016 Return-Path: Delivered-To: freebsd-stable@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 79A4DC0F315 for ; Wed, 12 Oct 2016 17:32:20 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: from mail-lf0-x22a.google.com (mail-lf0-x22a.google.com [IPv6:2a00:1450:4010:c07::22a]) (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 0E511CE9; Wed, 12 Oct 2016 17:32:20 +0000 (UTC) (envelope-from nparhar@gmail.com) Received: by mail-lf0-x22a.google.com with SMTP id b75so85969278lfg.3; Wed, 12 Oct 2016 10:32:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:subject:to:references:cc:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding; bh=1WbpoDfVjWL1x9WXB+GxeJ1TCvH4ckqy+Im3/UsmoiI=; b=cGo6X2LGrzmLcOLA4tFokWpUx0GojtUPSOCsai78MTxkEHdhRea+dlqPhOXS7yzelF 1Q18NdZNOoyItFfIU0BQK4jwKkaWisNltjExP5FvkVBF1LdPQm3TIk6mFFlFEFniIOUe twG6iE8eUXhgSCjZjRwyG1y5/xSXifOTomLqhlCT2BAaSF4OmFMHjR9OwXSBH21znWW6 FM1v4dskgV4X3yge/CpUHqiU6vJVgP5QdJmMC0uK+b+2ga34HTwiFXksbQUIea4stN3/ XnUW7PNBMfyAVOCsVsyR+YH1STIQZLnk5gaqJDCmLLTaunrLeX8PGFkIUZi+GfxcgvgG cGBw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:to:references:cc:from:message-id :date:user-agent:mime-version:in-reply-to:content-transfer-encoding; bh=1WbpoDfVjWL1x9WXB+GxeJ1TCvH4ckqy+Im3/UsmoiI=; b=a79PhgevpPSHnAeOwwmDq9T2n5qcFYG/jSy/NW6NnCLAdWeyVK0M75beUG7GX8Tokl isKDplWTLjGOKmAVoxP/oW/NfdgCTADiPSraqssFlW8fqOBb9sp1MdaL5s+CFjKtPUeo tFk+E583Zx0pqCjKP4stDcMtgAUKJOV+IJFwQ3rvhICdjGTHxJxCCWnoQ8VgcTtaFAGo krUvcuvKu1mjFhvdnk7xUN3d+lIWOqDNqUe8KOpobS+W6Udg8093fipbX87oNjfnNjBT DhldIzw1BdmdIdh4Bdx2Mv2LrdIq11K/9xSvWJfr93+vvFF2buSbmv1ZmtjJ5CRe/iq9 Rl5g== X-Gm-Message-State: AA6/9Rm/2Hp/PC7WvEeg4tB9WQOefo1zHNyocsjr11ZknwuAzFzUrD2Y6md5o1SgW6Kr/g== X-Received: by 10.25.32.69 with SMTP id g66mr2940237lfg.15.1476293538091; Wed, 12 Oct 2016 10:32:18 -0700 (PDT) Received: from [10.192.166.0] (stargate.chelsio.com. [12.32.117.8]) by smtp.googlemail.com with ESMTPSA id f198sm2569430lfe.10.2016.10.12.10.32.15 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 12 Oct 2016 10:32:17 -0700 (PDT) Sender: Navdeep Parhar Subject: Re: 11.0 stuck on high network load To: Julien Charbon , Slawa Olhovchenkov References: <20161006111043.GH54003@zxy.spb.ru> <1431484c-c00e-24c5-bd76-714be8ae5ed5@freebsd.org> <20161010133220.GU54003@zxy.spb.ru> <23f1200e-383e-befb-b76d-c88b3e1287b0@freebsd.org> <20161010142941.GV54003@zxy.spb.ru> <52d634aa-639c-bef7-1f10-c46dbadc4d85@freebsd.org> <20161010173531.GI6177@zxy.spb.ru> <8143cd8f-c007-2378-b004-b2b037402d03@freebsd.org> <20161011121145.GJ6177@zxy.spb.ru> <20161012084045.GA57714@zxy.spb.ru> Cc: Konstantin Belousov , freebsd-stable@FreeBSD.org, hiren panchasara From: Navdeep Parhar Message-ID: <121fe05f-37fb-9a65-1241-9206aed1e77a@FreeBSD.org> Date: Wed, 12 Oct 2016 10:32:14 -0700 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Oct 2016 17:32:20 -0000 > I see, thus just for the context: The TCP stack in sys/dev/cxgb* is a > TOE (TCP Offload Engine?) TCP stack for Chelsio NICs, it is a > separate/side TCP stack that is used only with TCP_OFFLOAD option. > > This TOE TCP stack actually has its own set of detach()/input() > functions and seems to check INP_DROPPED flag properly. I guess @np > check fixes in socket TCP stack and decides which one can also impact Yes, I do keep an eye on the changes in the stack and keep the TOE drivers up to date. The good part is that those drivers are trying to do the exact same thing with the locks and various bits of state as the software stack so they don't have any special requirements. If any patch comes out of this discussion I'll update the TOE drivers (if needed). btw, if you're looking at TOE drivers then read the sys/dev/cxgbe/t4_tom code (instead of the old T3 chip's cxgb/ulp/tom) as that's the most actively maintained and tested. Regards, Navdeep