But, the OS maintains a separate PC (program counter ),stack and A CPU
register state for a thread . So option A I am not sure is correct, it says
ONLY..
scheduling and accounting information is stored for a process right? Can you
please explain why C is not correct and D is correct?

On Tue, Jun 21, 2011 at 11:17 PM, rahul <rahulr...@gmail.com> wrote:

> A, D
>
> On Tue, Jun 21, 2011 at 11:16 PM, Akshata Sharma <
> akshatasharm...@gmail.com> wrote:
>
>>  A thread is usually defined as a ‘light weight process’ because an
>> operating system (OS) maintains smaller data structures for a thread than
>> for a process. In relation to this, which of the followings is TRUE?
>> (A) On per-thread basis, the OS maintains only CPU register state
>> (B) The OS does not maintain a separate stack for each thread
>> (C) On per-thread basis, the OS does not maintain virtual memory state
>> (D) On per thread basis, the OS maintains only scheduling and accounting
>> information
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Algorithm Geeks" group.
>> To post to this group, send email to algogeeks@googlegroups.com.
>> To unsubscribe from this group, send email to
>> algogeeks+unsubscr...@googlegroups.com.
>> For more options, visit this group at
>> http://groups.google.com/group/algogeeks?hl=en.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "Algorithm Geeks" group.
> To post to this group, send email to algogeeks@googlegroups.com.
> To unsubscribe from this group, send email to
> algogeeks+unsubscr...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/algogeeks?hl=en.
>

-- 
You received this message because you are subscribed to the Google Groups 
"Algorithm Geeks" group.
To post to this group, send email to algogeeks@googlegroups.com.
To unsubscribe from this group, send email to 
algogeeks+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/algogeeks?hl=en.

Reply via email to