From owner-freebsd-current@FreeBSD.ORG Sat Aug 18 19:23:37 2012 Return-Path: Delivered-To: current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id EAB6B106566B for ; Sat, 18 Aug 2012 19:23:37 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 429998FC0A for ; Sat, 18 Aug 2012 19:23:37 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:8870:d54b:33e8:55b2]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 999904AC2D; Sat, 18 Aug 2012 23:23:35 +0400 (MSK) Date: Sat, 18 Aug 2012 23:23:17 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <1116278226.20120818232317@serebryakov.spb.ru> To: Ian Lepore In-Reply-To: <1345215393.27688.85.camel@revolution.hippie.lan> References: <157941699.20120815004542@serebryakov.spb.ru> <502AE8B5.9090106@FreeBSD.org> <502B775D.7000101@FreeBSD.org> <1849591745.20120815144006@serebryakov.spb.ru> <1345139226.27688.48.camel@revolution.hippie.lan> <174138639.20120817143840@serebryakov.spb.ru> <1345215393.27688.85.camel@revolution.hippie.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: quoted-printable Cc: current@freebsd.org Subject: Re: CURRENT as gateway on not-so-fast hardware: where is a bottlneck? X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: lev@FreeBSD.org List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 18 Aug 2012 19:23:38 -0000 Hello, Ian. You wrote 17 =C1=D7=C7=D5=D3=D4=C1 2012 =C7., 18:56:33: IL> That result actually matches my expectation... it fixed only a part of IL> your problem. I was (partly) wrong :( Under ``really high'' load (4MiB/s up/down load in same time) userland freezes again. Unfortunately, it is difficult to repeat such load on request in y case, so I don't have KTR of scheduling in such case, but here is one thing I notice: when load is lower (like 2MiB/s both ways) ng_queue consume only 4-5% of CPU. And before freeze "top" shows ng_queue consumes about 60% of CPU. It is strange, as traffic goes up only at x2 rate... --=20 // Black Lion AKA Lev Serebryakov