Re: how to implement Thread Local Storage (TLS) in kernel
- From: "Don Burn" <burn@xxxxxxxxxxxxxxxx>
- Date: Wed, 15 Jun 2005 20:08:59 -0400
Lets see, there are a limited number of sockets ever opened, but thousands
of thread occur in a running system, uh your design has big flaws here.
Even if the above were not the case, how are you going to track this stuff
in the kernel?
--
Don Burn (MVP, Windows DDK)
Windows 2k/XP/2k3 Filesystem and Driver Consulting
Remove StopSpam from the email to reply
"Ben Kial" <benkial@xxxxxxxxxxx> wrote in message
news:1118871686.725736.181250@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
>I need to keep some access history information for user threads (like
> if
> this thread has opened an TCP/IP socket and where). The solution I can
> think of is to create a TLS in kernel, and store the access history
> when a thread is requesting such service.
>
>
> Ben
>
> P.S. Pavel: by the way, I don't belive Linux kernel has a TLS
> infrastructure
> either. So, moving my development to Linux won't help :-)...
>
.
- References:
- how to implement Thread Local Storage (TLS) in kernel
- From: Ben Kial
- Re: how to implement Thread Local Storage (TLS) in kernel
- From: Doron Holan [MS]
- Re: how to implement Thread Local Storage (TLS) in kernel
- From: Ben Kial
- Re: how to implement Thread Local Storage (TLS) in kernel
- From: Don Burn
- Re: how to implement Thread Local Storage (TLS) in kernel
- From: Ben Kial
- how to implement Thread Local Storage (TLS) in kernel
- Prev by Date: Re: XIP Support in Windows 2003
- Next by Date: Re: CreateProcess not working as doc specifies.
- Previous by thread: Re: how to implement Thread Local Storage (TLS) in kernel
- Next by thread: Re: how to implement Thread Local Storage (TLS) in kernel
- Index(es):
Relevant Pages
|