public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: John Aspinall <jgaspinall@rcn.com>
To: Rick Brown <rick.brown.3@gmail.com>
Cc: kernelnewbies <kernelnewbies@nl.linux.org>, linux-newbie@vger.kernel.org
Subject: Re: Threading in linux
Date: Tue, 24 Apr 2007 20:48:51 -0400	[thread overview]
Message-ID: <462EA573.8020509@rcn.com> (raw)
In-Reply-To: <7783925d0704240336i49e918dcm4d38e9bbc0310a39@mail.gmail.com>

Rick Brown wrote:
>
> Could you hint upon the kernel features required for NPTL? May be a link?

I know very little about this, but by coincidence (the application 
program I work on got a nice bugfix because of this) I can tell you one 
kernel difference on x86_64 kernels that support NPTL.

For NPTL on x86_64, the kernel reserves a register for thread-ID.  That 
register is swapped as part of the context switch the kernel does.  In 
the older LinuxThreads, thread-ID was established by looking up a stack 
address in a table.  In the LinuxThreads implementation, thread-ID was 
broken whenever a thread ran on the alt-stack.

John Aspinall
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

      parent reply	other threads:[~2007-04-25  0:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-24  6:38 Threading in linux Rick Brown
2007-04-24  7:03 ` pradeep singh
2007-04-24  7:17 ` Amol Lad
2007-04-24  8:29   ` Rick Brown
2007-04-24  9:54 ` Erik Mouw
2007-04-24 10:08 ` Mike Frysinger
2007-04-24 10:36   ` Rick Brown
2007-04-24 10:51     ` Mike Frysinger
2007-04-25  0:48     ` John Aspinall [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=462EA573.8020509@rcn.com \
    --to=jgaspinall@rcn.com \
    --cc=kernelnewbies@nl.linux.org \
    --cc=linux-newbie@vger.kernel.org \
    --cc=rick.brown.3@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