Give them a solid ground work I parallelism, probably one of the most
significant issues to be faced in SMP. How do you keep that other processor
from running the same DPC (or what ever it may be called) and running up
you’re back side and doing dirty on your data. Synchronization and
serialization of execution are all part of that.
Gary G. Little
Staff Engineer
Broadband Storage, Inc.
xxxxx@broadstor.com
-----Original Message-----
From: Jean Valentine [MS] [mailto:xxxxx@microsoft.com]
Sent: Thursday, October 11, 2001 12:39 AM
To: NT Developers Interest List
Subject: [ntdev] Re: What do we need to know as far as OS techniques go ?
One significant point - the concept of re-entrant, parallel code is very
important is little understood. I can’t tell you the number of times I’ve
seen code from a novice driver developer which seems to mostly run fine on a
single proc machine (with some intermittent, hard to track down problems)
and just rolls over and dies on a multi proc machine.
And if you can look at *why* memory allocation in C vs. C++ makes a
significant impact in kernel mode (i.e. non-paged pool size and clear
understanding of instantiation of a class with multiple inheritance), I
think this would be valuable.
Clarification of what is provided to applications by the kernel mode code,
and what is / is not available at this level. If you can keep just one
person from e-mailing me with “The DDK must be broken, 'cause I can’t get
my C++ floating point calls to work…” And if you can come up with an easy
to understand (ie for a non system level dev) way to explain *why* you can’t
use VB in a kernel mode driver, I’d love to have a copy <;-)
Jean
“Moreira, Alberto” wrote in message
news:xxxxx@ntdev…
>
>
> I’m going to stick my head out with this one, and this may be slightly
> off-topic, but what the heck ?
>
> You guys may not know, but I’m also a grad school computer science
teacher.
> I’m going to teach an “Advanced OS” course next Spring to Master Degree
> students. I want to strongly tilt it towards kernel mode development. My
> college has a battery of Win2K workstations, and several “electronic
> classrooms” with thirty or so PCs in them, so I’m not unwilling to teach
the
> students how to write a WDM driver. On the other hand, I’d like to keep
> their eyes open to Linux driver development too. And I want to target it
to
> a professional as opposed to theoretical tack, so that they can do some
real
> work during the course that prospective employers - like some of you 
-
> may eventually be interested in hiring them after they graduate.
>
> If nothing else, I want them to leave my course in a position to be able
to
> understand an OSR course, and immediately start programming after that.
>
> What do you think they should learn as far as WDM and Kernel Mode
> development is concerned ? What basic skills are needed for young
> professionals to get started in our kernel and driver development world ?
> How far is far enough in a 16-week two-hour-a-week lab course ?
>
> Your input is appreciated!
>
>
> Alberto.
>
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@broadstor.com
> To unsubscribe send a blank email to
leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
>
>
—
You are currently subscribed to ntdev as: xxxxx@broadstor.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com