From owner-freebsd-smp Tue May 15 15:38:21 2001 Delivered-To: freebsd-smp@freebsd.org Received: from hotmail.com (oe74.pav1.hotmail.com [64.4.30.209]) by hub.freebsd.org (Postfix) with ESMTP id 80D6537B423 for ; Tue, 15 May 2001 15:38:16 -0700 (PDT) (envelope-from claudevms@hotmail.com) Received: from mail pickup service by hotmail.com with Microsoft SMTPSVC; Tue, 15 May 2001 15:38:15 -0700 X-Originating-IP: [204.124.92.190] From: "Bruce Allen" To: Cc: Subject: Ready to code... When can I start? Date: Tue, 15 May 2001 16:39:45 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0007_01C0DD5D.A640DE60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Message-ID: X-OriginalArrivalTime: 15 May 2001 22:38:15.0792 (UTC) FILETIME=[BB3F3F00:01C0DD8F] Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0007_01C0DD5D.A640DE60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, Operating system internals are fun. I just wish I had more time - I'm = married! What can I work on? I once added context switching to PC-XINU for the = math co-processor. I have programmed in assembly language and I know C.=20 Has anyone looked at how VMS handles interrupts (HW and SW)? I have, but = I'm partial to VMS. How about how VMS does threading? Or perhaps how VMS has asynchronous = system traps (ASTs) for allowing the programmer to do asynchronous programming. NT stole = ASTs from VMS and=20 broke them. There's many ways to skin the cat - unless you are an animal = rights person. I would love to see FreeBSD implement an interrptable kernel and support = the execution of application code in kernel mode through a system call. The global lock approach I read = about on your site sounds=20 like how DOS serialized its I/O - yuk! Other OSes have good features = that FreeBSD could benefit from. The Lustre project is attempting to create a VMS-like distributed lock = manager for Linux. I am working on doing the same thing for FreeBSD since I like the FreeBSD license = agreement better. I am also working on how=20 to make a share everything cluster work on FreeBSD. I'm still in the = very early stages. What efforts need help? My current job is boring and I miss the hell out = of software development - however it pays well! Thanks, Bruce ------=_NextPart_000_0007_01C0DD5D.A640DE60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,

Operating system internals are fun. I just wish I = had more=20 time - I'm married!

What can I work on? I once added context switching = to PC-XINU=20 for the math co-processor.

I have programmed in assembly language and I know C. =

Has anyone looked at how VMS handles interrupts (HW = and SW)? I=20 have, but I'm partial to VMS.

How about how VMS does threading? Or perhaps how VMS = has=20 asynchronous system traps (ASTs)

for allowing the programmer to do asynchronous = programming. NT=20 stole ASTs from VMS and

broke them. There's many ways to skin the cat - = unless you are=20 an animal rights person.

I would love to see FreeBSD implement an = interrptable kernel=20 and support the execution of application code

in kernel mode through a system call. The global = lock approach=20 I read about on your site sounds

like how DOS serialized its I/O - yuk! Other OSes = have good=20 features that FreeBSD could benefit from.

The Lustre project is attempting to create a = VMS-like=20 distributed lock manager for Linux. I am working on

doing the same thing for FreeBSD since I like the = FreeBSD=20 license agreement better. I am also working on how

to make a share everything cluster work on FreeBSD. = I'm still=20 in the very early stages.

What efforts need help? My current job is boring and = I miss=20 the hell out of software development - however it pays = well!

Thanks,

Bruce

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