From owner-freebsd-stable@freebsd.org Thu Sep 14 01:54:58 2017 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 6E958E1C339 for ; Thu, 14 Sep 2017 01:54:58 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (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 2573C83D70; Thu, 14 Sep 2017 01:54:58 +0000 (UTC) (envelope-from sepherosa@gmail.com) Received: by mail-qk0-x233.google.com with SMTP id a128so4555458qkc.5; Wed, 13 Sep 2017 18:54:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=coWos+EU4Fb1qsu7GDY+R8a+fwee4Zd6cCjbRd3mZa8=; b=jxbG0YaImzQbTAOFiaP37mQXI5TpC3c++KCQTzV6woLnHjToQYwRwctlPyqrEFryEd ZF+rRCXQ+gkPnRBJVRRMqsZ0RTCz8NElVipR9To4qmNA5xsJIhOPCQ6HVC7o28YaiT4e MgZDLjyOerM+ImATmpkGBjXjeP/vo521BVeOmQhaQ/nCcmnMI3bjy9MNosInOqzSPSmo 4PDusbYcWwrLSRJzWbZgSAZgsW55BemFO63/Sckg9EsUreMSIPsrJQfSv1SHOA8MxHDh xeY5eWI/aLqHI6XAighmWh+gH5/gCgS6j5ZijG5/6R9003zDVO9C3KIvL6p2aWyzaz/A HGTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=coWos+EU4Fb1qsu7GDY+R8a+fwee4Zd6cCjbRd3mZa8=; b=dEtIDaA//xi74OOL4YXnUsjF9jQsVwKfuMmb4vmFD0/nTHdDZEfnTdeinKB2iZN+1k lX5CNUS30BCxJNo4aB2ryZ07Y5IZ169O10z1EjgBmSP5pQrns9cRVPXwXomhTaJol/Pz UGJxtqeh9Jvc+AJi7zlljx2wbCSMDqayExhJ2sjMAA63NfavCTCHzQc6W7zgz1FmyTQX 2wxPhFiinShtpglIWvOISxFuIdqE5KdOMkWPaje72AgcCvMH7TMcIXEICeKxsu3fSwSA idcjX3TTaZcvBXrILgV0A3ViBi6orBVimgiud4o2+HUC1UuE/6XxGia7BRhmi1YsVc39 vM2A== X-Gm-Message-State: AHPjjUilZW9phtNZ08eKFa4d8TsrKNMXtouauORU6+polFviRbkFGaZd kymhsTJF8KxQt3stiwhwJpa1B6Tr1t3CUS9i5w== X-Google-Smtp-Source: AOwi7QDehbs2lyLp03nayNasW5qiHjRktzeNc2J7+0J1er9HXZD5oPAWuot0JEsk1uZ8PaWSEsYzTaFhSDaGdiQoBuE= X-Received: by 10.55.71.6 with SMTP id u6mr607533qka.166.1505354097182; Wed, 13 Sep 2017 18:54:57 -0700 (PDT) MIME-Version: 1.0 Sender: sepherosa@gmail.com Received: by 10.140.21.20 with HTTP; Wed, 13 Sep 2017 18:54:56 -0700 (PDT) In-Reply-To: <20170908010400.0fb81bc4@akips.com> References: <20170906193309.796c79ed@akips.com> <3f96c7d0-4fbd-26cb-5c84-8868d12eb427@ingresso.co.uk> <14997bba-aac2-947b-9b78-04af41ea29b0@freebsd.org> <20170907150711.025e4e41@akips.com> <20170908010400.0fb81bc4@akips.com> From: Sepherosa Ziehau Date: Thu, 14 Sep 2017 09:54:56 +0800 X-Google-Sender-Auth: ShoHNLKRAIr2ilQUtTkwN2GnqI0 Message-ID: Subject: Re: 11.1 running on HyperV hn interface hangs To: Paul Koch Cc: Julian Elischer , freebsd-stable@freebsd.org, Hongjiang Zhang Content-Type: text/plain; charset="UTF-8" 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: Thu, 14 Sep 2017 01:54:58 -0000 If you have any updates on this, please let me know. There is still time for 10.4. On Thu, Sep 7, 2017 at 11:04 PM, Paul Koch wrote: > On Thu, 7 Sep 2017 13:51:11 +0800 > Sepherosa Ziehau wrote: > >> Weird, your traffic pattern does not even belong to anything heavy. >> Sending is mainly UDP, which will never be able to saturate the TX >> buffer ring causing the RXBUF ACK sending failure. This is weird. > > It's a bit tricky. The poller is very fast. We ping every device every 15 > seconds, and collect every MIB object every 60 seconds. The poller "rate > limits" itself by dividing each minute into 100ms time slots and only sends a > specific amount of pings/snmp packets in each time slot. The problem is, it > blasts the request packets out really fast at the start of each time slot, > and then sits in a receive loop until the next time slot comes around. The > requests are not paced over the 100ms, therefore it will blast out a lot > of packets in a few milliseconds. > > We use to use a 1 second rate limiting time slot, and didn't interlace > ping/snmp requests, but we found certain interface types on Cisco 6509 > switches couldn't keep up with back-to-back pings and would lose them. > > >> Anyhow, make sure to test this patch: >> 8762017-Sep-07 02:19 hn_inc_txbr.diff > > Yep. Might take a bit of time to test though because we'll need to get the > customer to spin up a test VM on the same platform, and they are fairly > remote (Perth, Australia). We don't run any Microsoft servers/HyperV setups > in our lab. > > Paul. > -- > Paul Koch | Founder | CEO > AKIPS Network Monitor | akips.com > Brisbane, Australia -- Tomorrow Will Never Die