www.microsoft.com ... The only time the OS is not "mapped" into the process address space is if you are running 32-bit code on a 64-bit OS. In that case it has to use an imitation syscall trampoline stored at the top of the 4GB 32-bit address space to jump into 64-bit mode to access the OS code. In all cases where you are running either 64-bit processes on a 64-bit OS or a 32-bit process on a 32-bit OS, the entire OS is mapped into the process address space.
The most pure example of a DCSS based OS is CMS, although the actual real OS (the CP part of CP/CMS) lives in a separate supervisor process. > -----Original Message----- > From: sqlite-users [mailto:sqlite-users-boun...@mailinglists.sqlite.org] > On Behalf Of James K. Lowden > Sent: Thursday, 16 February, 2017 11:30 > To: sqlite-users@mailinglists.sqlite.org > Subject: Re: [sqlite] Thread safety of serialized mode > > On Wed, 15 Feb 2017 07:55:16 -0700 > "Keith Medcalf" <kmedc...@dessus.com> wrote: > > > Note that for several modern OSes, the OS is nothing more than a > > discontiguous saved segment (DCSS) which is mapped into *every* > > process space and that process isolation is more of a myth than a > > reality. > > Are you referring to one in particular we could read about? > > --jkl > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
