mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: jimmy bahuleyan <knight.camelot@gmail.com>
To: "Ni@m" <niam.niam@gmail.com>
Cc: davids@webmaster.com, LKML <linux-kernel@vger.kernel.org>
Subject: Re: NPTL
Date: Thu, 12 Jul 2007 18:22:35 +0530	[thread overview]
Message-ID: <46962413.8060702@gmail.com> (raw)
In-Reply-To: <a9e22dff0707120537l1a29de93vdd67f146cf36a120@mail.gmail.com>

Ni@m wrote:
> So I can say that in linux 'thread' == 'process'?
> 

No. It's more like, in linux threads are visible to the kernel (unlike
in N:1 thread models, linux is 1:1). Threads are the basic unit of
scheduling.

A process can have >1 threads.

> Is kernel routine 'kthread' creating a process?
> I'm just thinking on this subject: if to create 'real threads' - will
> it increase performance? Should I ever think in this way?
> When I say 'real thread' - I mean the thread that doen't switch
> context when it's starting to run.
> 

What do you mean by context?

Each thread has it's own stack, registers, etc. which form it's context.
A process has more info like file descriptors, IPC resources, virtual
memory info. Between scheduling threads of the same process these stay same.

-jb
-- 
Tact is the art of making a point without making an enemy.

  parent reply	other threads:[~2007-07-12 12:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a9e22dff0707120518q16aeae73p2905226abbadd03d@mail.gmail.com>
2007-07-12 12:18 ` NPTL Ni@m
2007-07-12 12:27   ` NPTL David Schwartz
2007-07-12 12:37     ` NPTL Ni@m
2007-07-12 12:41       ` NPTL Peter Zijlstra
     [not found]         ` <a9e22dff0707120557t574f9383g5363c26074ea6d6a@mail.gmail.com>
2007-07-12 12:58           ` Fwd: NPTL Ni@m
2007-07-12 13:16             ` Bernd Petrovitsch
2007-07-12 16:48             ` Lennart Sorensen
2007-07-12 12:52       ` jimmy bahuleyan [this message]
2007-07-12 12:58       ` NPTL David Schwartz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46962413.8060702@gmail.com \
    --to=knight.camelot@gmail.com \
    --cc=davids@webmaster.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=niam.niam@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®