Linked by Thom Holwerda on Sat 19th Aug 2006 16:11 UTC
Microsoft MSDN's Channel 9 has two videos in their 'Going Deep' series which dive, well, deeper into Singularity, the operating system in development at Microsoft's research department. The first of the two is about, among other things, Software Isolated Processes (SIPs). The second of the two actually shows Singularity in action.
Thread beginning with comment 153936
To read all comments associated with this story, please click here.
by IceCubed on Sat 19th Aug 2006 16:34 UTC
Member since:

In video The kernel uses 17 048 Kbytes. 17Mbytes? Is this normal?

Reply Score: 1

RE: Kernel
by Eugenia on Sat 19th Aug 2006 16:36 in reply to "Kernel"
Eugenia Member since:

Modern kernels will use as much RAM as they can trying to make efficient use of whatever is available. So while a kernel might only need 2 MB, it might actually use 50.

Reply Parent Score: 1

RE[2]: Kernel
by SomeGuy on Sat 19th Aug 2006 20:25 in reply to "RE: Kernel"
SomeGuy Member since:

Wrong. The buffers aren't part of kernel memory, generally, any more than mapped pages from the filesystem are. They're usually managed by the VM system in the kernel for other application's use. Also, if it was buffering inside the kernel, I'd expect the kernel to actually show up as several hundred megs in size.

However, if all the code running is running in .NET IL, then there would have to be an entire VM in the kernel, as the alternative would be to have the VM statically compiled into each process as native code. This is probably the source of the relatively huge size of memory.

Edited 2006-08-19 20:43

Reply Parent Score: 3

RE: Kernel
by hobgoblin on Sat 19th Aug 2006 16:48 in reply to "Kernel"
hobgoblin Member since:

isnt every bit of code managed?

Reply Parent Score: 1

RE[2]: Kernel
by Bonus on Sat 19th Aug 2006 17:44 in reply to "RE: Kernel"
Bonus Member since:

I dont consider pointers managed.

Reply Parent Score: 1

RE: Kernel
by ma_d on Mon 21st Aug 2006 04:18 in reply to "Kernel"
ma_d Member since:

It's more complicated than that on other OS's. The default memory split up in NT is that the first 2GB can be reserved for the kernel (forgive me if I botch this). This is largely meaningless until you want to have a 2.1GB process of your own. TMK there is a way to set NT down to using less, but very few people are concerned with using 2GB of RAM on a single process.

I don't really understand calling the kernel a process anyway.

Reply Parent Score: 1