From owner-freebsd-smp  Fri Oct  6  9:36:19 2000
Delivered-To: freebsd-smp@freebsd.org
Received: from crewsoft.com (ns.aenet.net [157.22.214.1])
	by hub.freebsd.org (Postfix) with ESMTP id 7D17937B502
	for <freebsd-smp@freebsd.org>; Fri,  6 Oct 2000 09:36:11 -0700 (PDT)
Received: from [63.197.8.222] (HELO wireless-networks.com)
  by crewsoft.com (CommuniGate Pro SMTP 3.3b5)
  with ESMTP id 319753; Fri, 06 Oct 2000 09:38:03 -0700
Message-ID: <39DDFF70.E09EB724@wireless-networks.com>
Date: Fri, 06 Oct 2000 09:36:00 -0700
From: Cedric Berger <cedric@wireless-networks.com>
X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Bruce Evans <bde@zeta.org.au>
Cc: "Matthew N. Dodd" <winter@jurai.net>,
	Mark Murray <mark@grondar.za>, Jake Burkholder <jburkhol@home.com>,
	Boris Popov <bp@butya.kz>, freebsd-smp@FreeBSD.ORG
Subject: Re: Problems with kthread_exit() and SMPng
References: <Pine.BSF.4.21.0010061628010.1977-100000@besplex.bde.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-smp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org



Bruce Evans wrote:
> 
> On Thu, 5 Oct 2000, Matthew N. Dodd wrote:
> 
> > On Thu, 5 Oct 2000, Mark Murray wrote:
> > > There is another problem; printf's inside a kthread corrupt like
> > > crazy. They look very unthreadsafe.
> >
> > I've been thinking about a buffered printf.
> 
> Ugh.  printf has to be unbuffered so that it can be used for debugging.

I'm not at all aware of how printf works on FreeBSD,
but what about a "half-buffered" printf as it is found in most RTOS
(i.e. the whole printf() message is buffered, with only a single I/O 
write() call at the end) ?

Cedric


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-smp" in the body of the message