public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Love <rml@tech9.net>
To: Breno <brenosp@brasilsec.com.br>
Cc: Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: 1:1 M:N threading
Date: Sun, 14 Sep 2003 15:11:59 -0400	[thread overview]
Message-ID: <1063566718.24473.63.camel@localhost> (raw)
In-Reply-To: <000b01c37af0$402349a0$f8e4a7c8@bsb.virtua.com.br>

On Sun, 2003-09-14 at 14:44, Breno wrote:

> What kind of threading kernel 2.4 and 2.6 do ? 1:1 or M:N ?

Both do 1:1.

But nothing stops you from running an M:1 or M:N threading library in
user-space on top of the kernel abstraction.

	Robert Love



  parent reply	other threads:[~2003-09-14 19:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-14 18:44 1:1 M:N threading Breno
2003-09-14 19:06 ` Rémi Colinet
2003-09-14 19:08 ` Alan Cox
2003-09-14 19:11 ` Robert Love [this message]
2003-09-16 15:04   ` Memory allocation Breno
  -- strict thread matches above, loose matches on Subject: below --
2003-09-15  9:12 1:1 M:N threading jpo234
2003-09-15 14:07 ` Andrea Arcangeli

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=1063566718.24473.63.camel@localhost \
    --to=rml@tech9.net \
    --cc=brenosp@brasilsec.com.br \
    --cc=linux-kernel@vger.kernel.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