From owner-freebsd-current  Wed Jan 17 10: 2:38 2001
Delivered-To: freebsd-current@freebsd.org
Received: from freebsd.dk (freebsd.dk [212.242.42.178])
	by hub.freebsd.org (Postfix) with ESMTP
	id DDBC637B699; Wed, 17 Jan 2001 10:02:12 -0800 (PST)
Received: (from sos@localhost)
	by freebsd.dk (8.9.3/8.9.1) id TAA02435;
	Wed, 17 Jan 2001 19:02:06 +0100 (CET)
	(envelope-from sos)
From: Soren Schmidt <sos@freebsd.dk>
Message-Id: <200101171802.TAA02435@freebsd.dk>
Subject: Re: HEADS-UP: await/asleep removal imminent
In-Reply-To: <20010117092109.O7240@fw.wintelcom.net> from Alfred Perlstein at "Jan 17, 2001 09:21:09 am"
To: bright@wintelcom.net (Alfred Perlstein)
Date: Wed, 17 Jan 2001 19:02:06 +0100 (CET)
Cc: rjesup@wgate.com (Randell Jesup), arch@FreeBSD.ORG,
	current@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

It seems Alfred Perlstein wrote:
> > >> Peter Wemm and I suspect that ata doesn't need it.  Right now I'm
> > >> running several make -j128 buildworlds and buildkernels with this
> > >> patch to catch any ata problems.
> > 
> >         Ummmm...
> > 
> >         It seems to me from reading the man page for asleep/await that
> > they have significant utility, and that the real issue would be one of
> > code not using them, especially as people work to remove the Giant
> > lock for SMP.
> > 
> >         Or is the discussion in the man page wrong in some way?
> 
> The manpage is correct, but we've yet to see it used properly in
> the code with the exception of ata, and even with ata we're not
> sure if it's needed.

Uhm, well I tried removing it here, and now -current (on SMP HW)
fails in new "interesting" ways. The problem here is that
-current is not stable on SMP HW so the question is if this
change in behavior is to the better or to the worse...

I suggest creative manpower is used to stabilize -current, instead
of fine trimming which API's should stay or not...

-Søren


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