From owner-freebsd-stable@FreeBSD.ORG Tue Oct 31 19:00:47 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id C3EA516A407; Tue, 31 Oct 2006 19:00:47 +0000 (UTC) (envelope-from mi+mx@aldan.algebra.com) Received: from corbulon.video-collage.com (static-151-204-231-237.bos.east.verizon.net [151.204.231.237]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0347443DFF; Tue, 31 Oct 2006 18:58:02 +0000 (GMT) (envelope-from mi+mx@aldan.algebra.com) Received: from mteterin.us.murex.com (mx-broadway [38.98.68.18]) by corbulon.video-collage.com (8.13.8/8.13.8) with ESMTP id k9VIw1UI069314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Tue, 31 Oct 2006 13:58:01 -0500 (EST) (envelope-from mi+mx@aldan.algebra.com) From: Mikhail Teterin Organization: Virtual Estates, Inc. To: "Jack Vogel" Date: Tue, 31 Oct 2006 13:57:54 -0500 User-Agent: KMail/1.9.5 References: <200610282112.k9SLC0cC024602@corbulon.video-collage.com> <200610311307.27063.mi+mx@aldan.algebra.com> <2a41acea0610311049n1a8d7f92lef3cdb14cbfef7a3@mail.gmail.com> In-Reply-To: <2a41acea0610311049n1a8d7f92lef3cdb14cbfef7a3@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit Content-Disposition: inline Message-Id: <200610311357.55373.mi+mx@aldan.algebra.com> X-Virus-Scanned: ClamAV 0.88.4/2133/Tue Oct 31 05:42:29 2006 on corbulon.video-collage.com X-Virus-Status: Clean X-Scanned-By: MIMEDefang 2.43 Cc: stable@freebsd.org, re@freebsd.org, Mikhail Teterin Subject: Re: new em-driver still broken X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 31 Oct 2006 19:00:47 -0000 вівторок 31 жовтень 2006 13:49, Jack Vogel написав: > Scott's question still hasnt been answered, or if so I dont understand it. > If everything was working why were you trying to turn on polling? Because it was working poorly -- over 50% of the (combined) CPU time was spent in the kernel ("sys") instead of on compressing the data ("user"). Polling seems to promise relief exactly for such situations, so I tried to enable it. > And if the machine is unreachable over the net, what is happening ON > the machine at that point, does it emit any useful information? Nothing -- the screen (console) is not updated. If I leave top(1) running, I'll see INSANE amounts of CPU-time (1300% each, for example) getting attributed to the compressing programs -- after that top stops refreshing. Hitting a key (even Shift) on the console's keyboard wakes everything up for some time, and traffic resumes -- only to stall again a minute or so later... -mi