On Mon, 6 Nov 2000, therapy wrote:
>
>
> within native threads the fork mechanism is not used.
> [...]
> is no need to copy parent process pages, cause all
> threads are allowed (and have) to operate on the same copy.
>
> man clone
Yeap, it's much more clear now after reading this manpage, t
On Mon, 6 Nov 2000, therapy wrote:
>
>
> within native threads the fork mechanism is not used.
> [...]
> is no need to copy parent process pages, cause all
> threads are allowed (and have) to operate on the same copy.
>
> man clone
Yeap, it's much more clear now after reading this manpage,
> > this is due to the use of native threads by default in jdk1.3, which in
> > linux are spawn as processess... so, everything's still fine :-)
> >
> Well, I thought _native_ threads are implemented as threads ;), not
> processes. Isn't it less effective this way ? Forking is
> time-expensive...
> > this is due to the use of native threads by default in jdk1.3, which in
> > linux are spawn as processess... so, everything's still fine :-)
> >
> Well, I thought _native_ threads are implemented as threads ;), not
> processes. Isn't it less effective this way ? Forking is
> time-expensive..
4 matches
Mail list logo
