From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Current Thread mapping
Date: Mon, 16 Jan 2012 12:00:16 +0700 [thread overview]
Message-ID: <CAGdaadbArf_8bs5GNx_0zYuhfWyi8goE-ifKK_QOrZ3aXHqmWQ@mail.gmail.com> (raw)
In-Reply-To: <CAFtwHej=L26e3LRt+_G_vRkdA20qFNZAmcp6swg4kxNrtCkL4Q@mail.gmail.com>
Hi Santosh :)
On Sun, Jan 15, 2012 at 16:32, SaNtosh kuLkarni
<santosh.yesoptus@gmail.com> wrote:
> HI everyone just wanted to know whats the current?implementation?of user||
> kernel space thread mapping ...is it 1:1 or does it depend on the needs ?
> For example say if i have 12k user space thread running ,,,how many kernel
> space thread would be managing them... as far as i know there is 1:1 mappin
For NPTL based threading (Native Posix Threading Library), glibc and
linux kernel together maintain 1:1 mapping, that is one user mode
thread represented handled by one kernel mode thread.
Before NPTL, IIRC it's M:1, that is more than one user mode threads
are represented by one kernel mode thread. In user space, there's
somekind of "coordinator" or "master" that does cooperative switching
between threads. In NPTL, all threads are under the management of
Linux process scheduler directly.
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2012-01-16 5:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 9:32 Current Thread mapping SaNtosh kuLkarni
2012-01-15 9:56 ` rohan puri
2012-01-15 10:32 ` Andi
2012-01-15 13:37 ` SaNtosh kuLkarni
2012-01-16 5:00 ` Mulyadi Santosa [this message]
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=CAGdaadbArf_8bs5GNx_0zYuhfWyi8goE-ifKK_QOrZ3aXHqmWQ@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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;
as well as URLs for NNTP newsgroup(s).