On Wed, Oct 03, 2001 at 06:46:52PM -0700, Nathan Meyers wrote:
> On Wed, Oct 03, 2001 at 06:32:11PM -0700, Dan Kegel wrote:
> > root wrote:
> > The 2.4 kernel uses 32 bit process ids, so that shouldn't be a
> > problem. Are there other precious resources you're worried about?
> > If not, there's
On Wed, Oct 03, 2001 at 06:32:11PM -0700, Dan Kegel wrote:
> root wrote:
> >
> > On Wed, Oct 03, 2001 at 02:22:51PM -0700, Dan Kegel wrote:
> > > Nathan Meyers wrote:
> > > > The current Linux implementation of POSIX threads uses the clone() kernel
> > > > call for each thread, resulting in a 1-1
On Wed, Oct 03, 2001 at 06:50:48AM -0700, Avi Cherry wrote:
> At 2:16 PM +0200 10/3/01, Florent Coste wrote:
> >I'm not a kernel guru too,
> >
> >but what know is that :
> >java threads are mapped to posix threads (linuxthreads in the glibc). The
> >linuxthreads library uses the kernel threads, wh
At 2:16 PM +0200 10/3/01, Florent Coste wrote:
>I'm not a kernel guru too,
>
>but what know is that :
>java threads are mapped to posix threads (linuxthreads in the glibc). The
>linuxthreads library uses the kernel threads, which directly map
>into a 'process
>like' entry in the scheduler. (1-1 m
> In Linux:
> Well, I hope to hear it from you guys. ;) ... since it is not in the book
> that I have and I am not a kernel guru ... and how is it different between
> 2.2 and 2.4.
Hello all,
I'm not a kernel guru too,
but what know is that :
java threads are mapped to posix threads (linuxthread
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Re-Reading the O'Reilly book "Java Threads 2nd Edition by Scott Oaks and
Henry Wong", in summary:
In Windows:
* Threads are timesliced
* With SMP, each CPU will select a currently running thread
( page 147 ) ( Therefore, no need to do some native
