CareerCup

blocking of the entire process happens in ULT(user level thread) where the kernel is unaware about the process being split into two or more threads.

It WILL be blocked if the thread is implemented as a user level thread and will NOT be blocked if it is implemented as a kernel level thread.

I think the answer will depend on the fact that which threading model the system is implementing
1> if it is many to one model -- then it will block entire process.
2> or if it is one to one model -- then other thread will continue their execution

depends whether the other threads is waiting on an input from the previously blocked thread. then the other thread will also block. If all the threads are independent in their work, then they wont block

blocking of the entire process happens in ULT(user level thread) where the kernel is unaware about the process being split into two or more threads.

again stupid question.. what means "blocking entire process ?"

process consists of one or more threads. If, for example, a thread which processes the user input is busy on I/O then it would appear to the user that the process is "blocked".

It depends on your program logic if other threads should wait for the thread doing I/O operations at the moment..

Which one is the right and best answer. multiple answers are confusing me.

Kirans answer is the correct one.

Uniprocessor :
--> User level thread : entire process blocks but could be controlled at times using jacketing
--> Kernel level thread : no blocking

Multiprocessor :
No blocking

if machine is single processor, whole process will be blocked.

if machine is multi processor, whole process may not be blocked .

e.g. thread1 is executing on Processor 1 ( and thread blocked with I/O operation ), thread2 is executing on processor2 . thread1 & thread2 are executing independently so one thread may not block other thread .