From owner-freebsd-arch Mon Nov 29 12:11: 5 1999 Delivered-To: freebsd-arch@freebsd.org Received: from ns1.yes.no (ns1.yes.no [195.204.136.10]) by hub.freebsd.org (Postfix) with ESMTP id 0B00515184 for ; Mon, 29 Nov 1999 12:11:03 -0800 (PST) (envelope-from eivind@bitbox.follo.net) Received: from bitbox.follo.net (bitbox.follo.net [195.204.143.218]) by ns1.yes.no (8.9.3/8.9.3) with ESMTP id VAA23449 for ; Mon, 29 Nov 1999 21:11:00 +0100 (CET) Received: (from eivind@localhost) by bitbox.follo.net (8.8.8/8.8.6) id VAA65880 for freebsd-arch@freebsd.org; Mon, 29 Nov 1999 21:10:59 +0100 (MET) Received: from peach.ocn.ne.jp (peach.ocn.ne.jp [210.145.254.87]) by hub.freebsd.org (Postfix) with ESMTP id 2323A15184 for ; Mon, 29 Nov 1999 12:10:53 -0800 (PST) (envelope-from dcs@newsguy.com) Received: from newsguy.com (p28-dn02kiryunisiki.gunma.ocn.ne.jp [210.163.200.125]) by peach.ocn.ne.jp (8.9.1a/OCN) with ESMTP id FAA21397 for ; Tue, 30 Nov 1999 05:10:52 +0900 (JST) Message-ID: <3842DBB5.8AFC9B6@newsguy.com> Date: Tue, 30 Nov 1999 05:01:57 +0900 From: "Daniel C. Sobral" X-Mailer: Mozilla 4.7 [en] (Win98; I) X-Accept-Language: en,pt-BR,ja MIME-Version: 1.0 To: freebsd-arch@freebsd.org Subject: Threads and the scheduler Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I have a question. Our scheduler is based on the assumption that i/o bound processes will block, and cpu bound processes will not. Because of that, we can support a _lot_ of i/o bound processes on a 64 Hz scheduler. If, though, we allow the i/o bound processes to always make use of their full quanta through use of threads, won't this have a huge impact on our ability to support many i/o bound processes? So, I guess what I'm getting at is: won't the proposed thread model have an impact on the effectiveness of our scheduler? -- Daniel C. Sobral (8-DCS) who is as social as a wampas dcs@newsguy.com dcs@freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message