From owner-freebsd-current Sat Sep 2 1: 6:11 2000 Delivered-To: freebsd-current@freebsd.org Received: from smtp02.iafrica.com (smtp02.iafrica.com [196.7.0.140]) by hub.freebsd.org (Postfix) with ESMTP id 00AF337B423; Sat, 2 Sep 2000 01:06:06 -0700 (PDT) Received: from [196.7.18.138] (helo=grimreaper.grondar.za ident=root) by smtp02.iafrica.com with esmtp (Exim 1.92 #1) id 13V8JD-00094s-00; Sat, 2 Sep 2000 10:05:51 +0200 Received: from grimreaper.grondar.za (mark@localhost [127.0.0.1]) by grimreaper.grondar.za (8.11.0/8.11.0) with ESMTP id e8286px12359; Sat, 2 Sep 2000 10:06:51 +0200 (SAST) (envelope-from mark@grimreaper.grondar.za) Message-Id: <200009020806.e8286px12359@grimreaper.grondar.za> To: Kris Kennaway Cc: Sheldon Hearn , Paul Herman , freebsd-current@FreeBSD.ORG Subject: Re: Current jumpieness References: In-Reply-To: ; from Kris Kennaway "Fri, 01 Sep 2000 03:33:54 MST." Date: Sat, 02 Sep 2000 10:06:51 +0200 From: Mark Murray Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What makes you say that? Are you seeing the problem as well? > > Not definitively, but many others have also complained since it went > in. It's one of the things Mark is trying to address by moving it to a > kthread. It _is_ most likely the random device, and I have a kthread improvement; however kthreads are currently cooperative, not preemptive, so the code "feels" similar[1]. I hold high hopes for the SMPng project fixing this (for UP and MP). [1] there are some hacks-and-kluges that can work around this, but they are gross. M -- Mark Murray Join the anti-SPAM movement: http://www.cauce.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message