Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 289
  • Last Modified:

Windows server 2008 R2 - Internals

MemoryI am interested in digging deeper on the internals of Windows server 2008 R2:  
non-page memory, threads, processes etc.

I have bought the Sys Internal books but they are bit over my head.

Any suggestions on how to decipher like:  kernel memory -  nonpaged ,etc
Picture attached.
0
techgenious
Asked:
techgenious
  • 3
  • 2
1 Solution
 
TheGeezer2010Commented:
0
 
techgeniousAuthor Commented:
Tried that also
0
 
TheGeezer2010Commented:
Not sure what you are asking here but here goes :-

Non-Paged memory will host threads from programs which cannot be swapped out of memory - they have to be continuously loaded in memory. Kernel mode drivers are an example of this.

Paged memory will host threads of programs which can be paged or swapped out to page file when not in active use.

You can use talk manager to show the individual threads for each of these catagories (view-columns-select the two columns to display).

The following is from here :-

http://serverfault.com/questions/27248/what-is-a-process-handle

A process handle is an integer value that identifies a process to Windows. The Win32 API calls them a HANDLE; handles to windows are called HWND and handles to modules HMODULE.

Threads inside processes have a thread handle, and files and other resources (such as registry keys) have handles also.

The handle count you see in Task Manager is "the number of object handles in the process's object table". In effect, this is the sum of all handles that this process has open.

If you do not release your handle to a resource, other people may not be able to access it - this is why you sometimes cannot delete a file because Windows claims it is in use (check out this article on handle leaks and Process Explorer).

Also, there is a per-process limit on various handles. Here is an example.

In general, if you are opening handles and not closing them, it is analogous to leaking memory. You should figure out what is going on and fix it.

Not sure what else you want to know ?
0
 
techgeniousAuthor Commented:
That helps alot, are there any  books that explain simple and helps with tools.

The sys internal books right now are over my head.
0
 
techgeniousAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for wynnie2's comment #a38351874

for the following reason:

great answer
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now