From: Christoph Hellwig <hch@caldera.de>
To: Anumula Venkat <anumulavenkat@yahoo.com>
Cc: linux-mm@kvack.org
Subject: Re: Thread specific data
Date: Sun, 16 Dec 2001 16:09:55 +0100 [thread overview]
Message-ID: <20011216160955.A21103@caldera.de> (raw)
In-Reply-To: <20011216125219.1450.qmail@web12004.mail.yahoo.com>; from anumulavenkat@yahoo.com on Sun, Dec 16, 2001 at 04:52:19AM -0800
On Sun, Dec 16, 2001 at 04:52:19AM -0800, Anumula Venkat wrote:
> Hello Friends,
>
> Can somebody help in knowing how to access thread
> data structures on kernel side.i.e accessing thread
> specific data in stack segment.
The Linux kernel has a unified process/thread concept so there isn't
really a 'thread data structure' in the kernel. See linux/sched.h
for details.
For userspace stack this is handle by glibc/linuxthreads. On i686
it uses sys_modify_ldt to get per-thread segments, not sure how it
is handled on older CPUs / other architectures.
Christoph
--
Of course it doesn't work. We've performed a software upgrade.
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
prev parent reply other threads:[~2001-12-16 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-16 12:52 Anumula Venkat
2001-12-16 15:09 ` Christoph Hellwig [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=20011216160955.A21103@caldera.de \
--to=hch@caldera.de \
--cc=anumulavenkat@yahoo.com \
--cc=linux-mm@kvack.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