title: Linux Kernel: Threading vs Process - task_struct vs thread_info
body: <p>I read that Linux does not support the concept of threads or light-weight processes and that it considers kernel threads just like any other process. However this principle is not very accurately reflected inside the code. We see task_struct that holds state information of a process (correct me if wrong) and also thread_info appended to the bottom of a process' kernel stack.</p>
  
  <p>Now the question is why does the code support the concept of individual threading through <strong>thread_info</strong> when linux is supposed to interpret threads like any other process? </p>
  
  <p>Please let me know what I am missing here - I am a newbie to linux kernel dev.</p>