From owner-freebsd-stable@FreeBSD.ORG Wed Nov 1 14:26:13 2006 Return-Path: X-Original-To: freebsd-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 8B89D16A403 for ; Wed, 1 Nov 2006 14:26:13 +0000 (UTC) (envelope-from freebsd-stable@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 302F643D5A for ; Wed, 1 Nov 2006 14:26:11 +0000 (GMT) (envelope-from freebsd-stable@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1GfH2I-0007Is-A8 for freebsd-stable@freebsd.org; Wed, 01 Nov 2006 15:25:47 +0100 Received: from 89-172-42-208.adsl.net.t-com.hr ([89.172.42.208]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Nov 2006 15:25:46 +0100 Received: from ivoras by 89-172-42-208.adsl.net.t-com.hr with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 01 Nov 2006 15:25:46 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-stable@freebsd.org From: Ivan Voras Date: Wed, 01 Nov 2006 15:25:28 +0100 Lines: 8 Message-ID: References: <200610282112.k9SLC0cC024602@corbulon.video-collage.com> <20061101015738.090863a2@loki.starkstrom.lan> <2a41acea0610311741w653d5bfdhad49d2f606a7cffe@mail.gmail.com> <200611010753.55556@aldan> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: 89-172-42-208.adsl.net.t-com.hr User-Agent: Thunderbird 1.5.0.7 (Windows/20060909) In-Reply-To: <200611010753.55556@aldan> Sender: news 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: Wed, 01 Nov 2006 14:26:13 -0000 Mikhail Teterin wrote: > Why would the scheduler affect the "sys" component of the load (which > shoots to the sky before the machine drops of the network)? I thought, > it only matters for user-space programs (the order in which they run)... It also schedules internal kernel threads (such as device driver interrupt threads, etc.)