From owner-freebsd-stable Mon Jan 24 8:11:36 2000 Delivered-To: freebsd-stable@freebsd.org Received: from kci.kciLink.com (kci.kciLink.com [204.117.82.1]) by hub.freebsd.org (Postfix) with ESMTP id D473E15CF4 for ; Mon, 24 Jan 2000 08:11:33 -0800 (PST) (envelope-from khera@kciLink.com) Received: from onceler.kcilink.com (onceler.kciLink.com [204.117.82.2]) by kci.kciLink.com (Postfix) with ESMTP id CCE58E8A4 for ; Mon, 24 Jan 2000 11:11:26 -0500 (EST) Received: (from khera@localhost) by onceler.kcilink.com (8.9.3/8.9.3) id LAA43101; Mon, 24 Jan 2000 11:11:26 -0500 (EST) (envelope-from khera@kci.kcilink.com) From: Vivek Khera MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <14476.31150.689748.108097@onceler.kcilink.com> Date: Mon, 24 Jan 2000 11:11:26 -0500 (EST) To: stable@FreeBSD.ORG Subject: Re: kern/13644 In-Reply-To: <200001231948.UAA01010@queeg.ludd.luth.se> References: <200001231636.LAA43285@rtfm.newton> <200001231948.UAA01010@queeg.ludd.luth.se> X-Mailer: VM 6.72 under 21.1 (patch 8) "Bryce Canyon" XEmacs Lucid Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >>>>> "MP" == Mattias Pantzare writes: MP> The problem is simply that the kernel that has a lower resolution on it's MP> scheduling than the clock that you are using, and that it takes time to do MP> things on a noral CPU. Plus the fact that FreeBSD is *not* a real-time OS, so any time guarantees are not really guarantees, just suggestions. If you want hard real-time constraints, you'll need to use a real-time OS. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message