From owner-freebsd-arch Fri Jun 21 18:11:24 2002 Delivered-To: freebsd-arch@freebsd.org Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by hub.freebsd.org (Postfix) with ESMTP id 6099B37B412 for ; Fri, 21 Jun 2002 18:11:22 -0700 (PDT) Received: by elvis.mu.org (Postfix, from userid 1192) id 36A4FAE2CF; Fri, 21 Jun 2002 18:11:22 -0700 (PDT) Date: Fri, 21 Jun 2002 18:11:22 -0700 From: Alfred Perlstein To: Julian Elischer Cc: Terry Lambert , Gary Thorpe , freebsd-arch@freebsd.org Subject: Re: multiple threads for interrupts Message-ID: <20020622011122.GF37053@elvis.mu.org> References: <20020621233754.GC37053@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.27i Sender: owner-freebsd-arch@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG * Julian Elischer [020621 17:40] wrote: > I have a tricky linked list (read thread run queue) corruption problem > I''ve been chasing for a couple of days.. > > it only shows up under moderate load.. e.g. 20 threaded processes, each > with > 3 kernel threads. > I'm closing in though.. Does it cause problems when no threads are active (just processes)? Basically I'd love to see this committed already if the base stability issues are mostly cleaned up. If threads cause issues then that's ok isn't it? -Alfred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message