From owner-freebsd-current@FreeBSD.ORG Fri Aug 17 10:39:06 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 36EBF106564A for ; Fri, 17 Aug 2012 10:39:06 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id E370B8FC0C for ; Fri, 17 Aug 2012 10:39:05 +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 9B4BF4AC2D; Fri, 17 Aug 2012 14:38:57 +0400 (MSK) Date: Fri, 17 Aug 2012 14:38:40 +0400 From: Lev Serebryakov Organization: FreeBSD X-Priority: 3 (Normal) Message-ID: <174138639.20120817143840@serebryakov.spb.ru> To: Ian Lepore In-Reply-To: <1345139226.27688.48.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> 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: Fri, 17 Aug 2012 10:39:06 -0000 Hello, Ian. You wrote 16 =C1=D7=C7=D5=D3=D4=C1 2012 =C7., 21:47:06: IL> It's a long shot, but if the trouble you're seeing has the same cause, IL> it should be fixed by this patch: IL> http://lists.freebsd.org/pipermail/freebsd-hackers/2012-January/037233.= html It looks like, this patch fixes freezes under network load. I could not repeat freezes now (except when `ktrdump' works, but I think, it is Ok). It also change "top" layout of processes: em0 tasq is not on the top now, and system have enough idel time even under load. But WiFi is affected by wire traffic :( --=20 // Black Lion AKA Lev Serebryakov