Email List: Xaustin-group-futures-lX
[All Lists]

Re: thread-private working directory

To: Alexander Terekhov <yyyyyyyy@xxxxxxxxxx>
Subject: Re: thread-private working directory
From: Kaz Kylheku <yyy@xxxxxxxxxxxxxxxxxxx>
Date: Fri, 1 Aug 2003 09:19:27 -0700 (PDT)
Cc: yyyyyyyyyyyyyyyyyyyyyy@xxxxxxxxxxxxx, <yyyyyyyyyyyyyy@xxxxxxxxxxxxx>
On Fri, 1 Aug 2003, Alexander Terekhov wrote:

> Harti Brandt wrote:
> [...]
> > I wonder how one would implement a per-thread current directory 
> > in an environment where there is no 1:1 mapping between user 
> > threads and kernel threads.
> 
> Something similar to (but probably a bit less convoluted ;-) ) 
> a per-thread signal mask, I guess.

What you can do is make the system calls take an extra parameter: a
context token designating the current directory relative to which paths
are to be resolved. The user space can then associate these tokens with
schedulable entitites. They are not visible through the library
interface, which makes the contexts implicit.

<Prev in Thread] Current Thread [Next in Thread>