From owner-freebsd-arch Tue Jul 10 5:24:22 2001 Delivered-To: freebsd-arch@freebsd.org Received: from pcnet1.pcnet.com (pcnet1.pcnet.com [204.213.232.3]) by hub.freebsd.org (Postfix) with ESMTP id 3B9AD37B403 for ; Tue, 10 Jul 2001 05:24:17 -0700 (PDT) (envelope-from eischen@vigrid.com) Received: (from eischen@localhost) by pcnet1.pcnet.com (8.8.7/PCNet) id IAA07387; Tue, 10 Jul 2001 08:23:34 -0400 (EDT) Date: Tue, 10 Jul 2001 08:23:33 -0400 (EDT) From: Daniel Eischen To: Julian Elischer Cc: Jason Evans , arch@FreeBSD.ORG Subject: Re: help needed in threads.. (Signals) In-Reply-To: <3B4A9AC1.BE93ECCF@elischer.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 On Mon, 9 Jul 2001, Julian Elischer wrote: > Daniel Eischen wrote: > > > > Does each KSE always start (after being preempted) with an upcall? > > This is up for discussion but generally: > yes OK, good. This allows the upcall to look for any pending messages (from other KSEs) before it resumes/starts a thread. > > We don't want to use the Linux method of communication between > > threads (using signals). I just want to make sure that we have > > all the tools necessary to make this work. > > > > how threads communicate with each other when they are on different processors > is tricky.. > what is wrong with 'shared memory'? > > All that a signal can do is leave a flag for the mainline to find > which is effectively shared memory anyhow.. Right, it just makes it harder because you may have to use locks to protect this 'shared memory', and you'll be doing this from the UTS (upcall). If there was a general way to send messages between KSEs, I think it would be a lot cleaner. But if each each KSE is always started with an upcall, then that gives it a chance to look for any pending messages. -- Dan Eischen To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-arch" in the body of the message