Windows and non-page memory - WAS: Minister promises that Part III is coming
David Biggins
ukcrypto at chiark.greenend.org.uk
Thu, 18 May 2006 10:19:13 +0100
This is a multi-part message in MIME format.
------_=_NextPart_001_01C67A5C.215E1392
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
=20
________________________________
From: ukcrypto-admin@chiark.greenend.org.uk
[mailto:ukcrypto-admin@chiark.greenend.org.uk] On Behalf Of John Brazier
Sent: 17 May 2006 22:49
To: ukcrypto@chiark.greenend.org.uk
Subject: RE: Windows and non-page memory - WAS: Minister
promises that Part III is coming
=09
=09
Perhaps so, but am I completely wrong in my insistence that what
has been touted as a definitive Windows 32 memory architecture paper
seems to be inaccurate, and thus MS are wrong to tout it as accurate?=20
I can see what you mean.
=20
To defend MS (god knows why) the article is primarily on memory mapped
files, not kernel architecture, and the article is from the perspective
of the "Win32" programmer - which is usually used in MS documentation
specifically to refer to the application-layer API, rather than to the
system architecture as a whole. And MS do not exactly encourage Win32
programmers to delve down to DDK level. Yes, the diagram should
perhaps have had some boxes that suggested that the NT kernel was less
monolithic than that and had its own API, but from the perspective of
the Win32 API programmer, once it's inside the kernel, that's it.
=20
Dave.
------_=_NextPart_001_01C67A5C.215E1392
Content-Type: text/html;
charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns=3D"http://www.w3.org/TR/REC-html40" xmlns:o =3D=20
"urn:schemas-microsoft-com:office:office" xmlns:w =3D=20
"urn:schemas-microsoft-com:office:word"><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<META content=3D"MSHTML 6.00.2900.2873" name=3DGENERATOR>
<STYLE>@font-face {
font-family: Tahoma;
}
@page Section1 {size: 8.5in 11.0in; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: "Times New Roman"
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle18 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
</STYLE>
</HEAD>
<BODY lang=3DEN-US=20
style=3D"WORD-WRAP: break-word; khtml-nbsp-mode: space; =
khtml-line-break: after-white-space"=20
vLink=3Dpurple link=3Dblue>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D245121608-18052006><FONT =
face=3DArial=20
color=3D#0000ff size=3D2></FONT></SPAN> </DIV><FONT face=3DArial =
color=3D#0000ff=20
size=3D2></FONT><BR>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px =
solid; MARGIN-RIGHT: 0px">
<DIV class=3DOutlookMessageHeader lang=3Den-us dir=3Dltr align=3Dleft>
<HR tabIndex=3D-1>
<FONT face=3DTahoma size=3D2><B>From:</B> =
ukcrypto-admin@chiark.greenend.org.uk=20
[mailto:ukcrypto-admin@chiark.greenend.org.uk] <B>On Behalf Of =
</B>John=20
Brazier<BR><B>Sent:</B> 17 May 2006 22:49<BR><B>To:</B>=20
ukcrypto@chiark.greenend.org.uk<BR><B>Subject:</B> RE: Windows and =
non-page=20
memory - WAS: Minister promises that Part III is =
coming<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D062244421-17052006><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2>Perhaps so, but am I completely wrong =
in my=20
insistence that what has been touted as a definitive Windows 32 memory =
architecture paper seems to be inaccurate, and thus MS are wrong to =
tout it as=20
accurate?<SPAN=20
=
class=3D245121608-18052006> </SPAN></FONT></FONT></FONT></SPAN></DIV=
></BLOCKQUOTE>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D062244421-17052006><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN class=3D245121608-18052006>I can =
see what you=20
mean.</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D062244421-17052006><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D245121608-18052006></SPAN></FONT></FONT></FONT></SPAN> </DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D062244421-17052006><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN class=3D245121608-18052006>To =
defend MS (god=20
knows why) </SPAN></FONT></FONT></FONT></SPAN><SPAN=20
class=3D062244421-17052006><FONT face=3DArial><FONT =
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D245121608-18052006>the article is primarily on memory mapped =
files, =20
not kernel architecture, and the article is from the perspective of the=20
"Win32" programmer - which is usually used in MS documentation =
specifically to refer to the application-layer API, rather than to the =
system=20
architecture as a whole. And MS do not exactly encourage =
Win32=20
programmers to delve down to DDK level. =20
</SPAN></FONT></FONT></FONT></SPAN><SPAN =
class=3D062244421-17052006><FONT=20
face=3DArial><FONT color=3D#0000ff><FONT size=3D2><SPAN =
class=3D245121608-18052006>Yes,=20
the diagram should perhaps have had some boxes that suggested that the =
NT kernel=20
was less monolithic than that and had its own API, but from the=20
perspective of the Win32 API programmer, once it's inside the kernel, =
that's=20
it.</SPAN></FONT></FONT></FONT></SPAN></DIV>
<DIV dir=3Dltr align=3Dleft><SPAN class=3D062244421-17052006><FONT =
face=3DArial><FONT=20
color=3D#0000ff><FONT size=3D2><SPAN=20
class=3D245121608-18052006></SPAN></FONT></FONT></FONT></SPAN> </DIV=
>
<DIV dir=3Dltr align=3Dleft><SPAN=20
style=3D"FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><SPAN=20
class=3D390395716-16052006><SPAN class=3D426543608-17052006><SPAN=20
class=3D245121608-18052006>Dave.</SPAN></SPAN></SPAN></SPAN></DIV></BODY>=
</HTML>
------_=_NextPart_001_01C67A5C.215E1392--