From owner-freebsd-current  Tue Oct 20 20:12:47 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id UAA08395
          for freebsd-current-outgoing; Tue, 20 Oct 1998 20:12:47 -0700 (PDT)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA08389;
          Tue, 20 Oct 1998 20:12:45 -0700 (PDT)
          (envelope-from julian@whistle.com)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id UAA27299;
	Tue, 20 Oct 1998 20:02:46 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpdB27297; Wed Oct 21 03:02:39 1998
Message-ID: <362D4EC7.167EB0E7@whistle.com>
Date: Tue, 20 Oct 1998 20:02:31 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2.7-RELEASE i386)
MIME-Version: 1.0
To: sos@FreeBSD.ORG
CC: current@FreeBSD.ORG
Subject: Re: softupdates/smp
References: <199810180918.LAA12711@sos.freebsd.dk>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

S?ren Schmidt wrote:
> 
> In reply to Julian Elischer who wrote:
> > Well  I'm doing it, but I've 'left off' development until the
> > ELF/CAM/3.0/etc  changes all settle down.
> >
> > looks to me as if someone has broken it again.
> > I'll be in europe for  a fortnight. When I get back
> > I hope things will have settled down enough for me to look at it again.
> 
> Erhm, I've never seen it work reliably under SMP, did you ever get the
> giant lock prims into the syncer ??
> 
> -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
> Søren Schmidt               (sos@FreeBSD.org)               FreeBSD Core Team
>                 Even more code to hack -- will it ever end?
> ..

As the syncer is a kernel thread and always in the kernel, it can only
be scheduled if it already has the lock. At least that is my
understanding.

I have no proof of this however. as I haven't looked at 
the 'giant lock' code..  If this is not true we have other problems.

Who knows about the "GL" code?

julian

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