Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 09 Jul 2001 11:08:37 -0700
From:      Terry Lambert <tlambert2@mindspring.com>
To:        John Baldwin <jhb@FreeBSD.ORG>
Cc:        Julian Elischer <julian@elischer.org>, current@FreeBSD.ORG, Jason Evans <jasone@canonware.com>, Peter Wemm <peter@wemm.org>
Subject:   Re: RFC: Kernel thread system nomenclature.
Message-ID:  <3B49F325.E2C6FEC8@mindspring.com>
References:  <XFMail.010706152734.jhb@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
John Baldwin wrote:
> >#3    struct upctx (upcall-context), virtcpu, thrdslot (thread slot)
> >#4    struct lwp    (decided)
> >
> > usually the 'lwp' will be passed around so diffs to NetBSD will be
> > minimalised.
> 
> One thing to note is that as Vahalia (sp?) points out, lwp
> on SVR4 and Solaris is actually #3 (a virtual CPU) where as
> lwp on SunOS is a user-thread.  Unfortunately, I think by
> using overloaded terms you are going to confuse people who
> come into the project from different backgrounds.  I would
> try and stay with non-ambiguous names if possible.

Virtual CPUs are a very bad idea.

The main reason SVR4 and Solaris threading didn't scale
well from day one is the "virtual CPU" approach.

-- Terry

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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3B49F325.E2C6FEC8>