public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: John Levon <movement@marcelothewonderpenguin.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel: ldt allocation failed
Date: Wed, 6 Feb 2002 16:29:09 +0000	[thread overview]
Message-ID: <20020206162909.GA68254@compsoc.man.ac.uk> (raw)
In-Reply-To: <Pine.LNX.3.96.1020206105011.7298A-100000@gatekeeper.tmr.com> <E16YUcn-0005bZ-00@the-village.bc.nu>
In-Reply-To: <E16YUcn-0005bZ-00@the-village.bc.nu>

On Wed, Feb 06, 2002 at 04:08:45PM +0000, Alan Cox wrote:

> Actually Jakub has already replied to my email with a glibc folks paper
> on the thread stuff (confusingly called tls just to confuse everyone who

where can we find this ?

thanks
john

-- 
"Mathemeticians stand on each other's shoulders while computer scientists
 stand on each other's toes."
	- Richard Hamming

  reply	other threads:[~2002-02-06 16:29 UTC|newest]

Thread overview: 46+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.21.0112070057480.20196-100000@tombigbee.pixar.com.suse.lists.linux.kernel>
     [not found] ` <5.1.0.14.2.20011207092244.049f6720@pop.cus.cam.ac.uk.suse.lists.linux.kernel>
     [not found]   ` <200202061258.g16CwGt31197@Port.imtp.ilyichevsk.odessa.ua.suse.lists.linux.kernel>
2002-02-06 13:19     ` kernel: ldt allocation failed Andi Kleen
2002-02-06 14:06       ` Dave Jones
2002-02-06 14:13       ` Alan Cox
2002-02-06 14:09         ` Andi Kleen
2002-02-06 14:39           ` Alan Cox
2002-02-06 16:37             ` bert hubert
2002-02-06 15:51         ` Bill Davidsen
2002-02-06 16:08           ` Alan Cox
2002-02-06 16:29             ` John Levon [this message]
2002-02-06 18:01               ` Alan Cox
2002-02-06 18:02       ` Denis Vlasenko
2002-02-06 15:12         ` Jakub Jelinek
2002-02-06 18:11           ` Maciej W. Rozycki
2002-02-06 20:19           ` H. Peter Anvin
2002-02-06 21:15             ` Jakub Jelinek
2002-02-06 21:17               ` H. Peter Anvin
2002-02-06 20:21           ` yodaiken
2002-02-06 21:00             ` H. Peter Anvin
2002-02-06 21:31               ` Jakub Jelinek
2002-02-06 22:05                 ` H. Peter Anvin
2002-02-06 22:20                   ` Jakub Jelinek
2002-02-06 23:35                     ` H. Peter Anvin
2002-02-07  0:21                 ` Alan Cox
2002-02-07  0:12                   ` Jakub Jelinek
2002-02-07  0:15                     ` H. Peter Anvin
2002-02-07  0:13                   ` H. Peter Anvin
2002-02-06 15:37         ` Alan Cox
     [not found] <fa.kit1f7v.j024op@ifi.uio.no>
2001-12-07  7:24 ` Dan Maas
2001-12-07  9:00   ` Kiril Vidimce
2001-12-07  9:15     ` Alan Cox
2001-12-07  9:13       ` Kiril Vidimce
2001-12-07  9:28         ` Alan Cox
2001-12-07  9:26       ` James Davies
2001-12-07  9:43         ` Alan Cox
2001-12-07 13:10           ` James Davies
2001-12-07 13:41             ` Dave Jones
2001-12-07 13:59               ` James Davies
2001-12-07 13:53             ` Alan Cox
2001-12-07  9:45     ` Anton Altaparmakov
2001-12-07 10:38       ` Alan Cox
2002-02-06 16:58       ` Denis Vlasenko
2002-02-06 13:42         ` Alan Cox
2002-02-06 17:20           ` Christoph Hellwig
2001-12-07 10:12     ` Anton Altaparmakov
2001-12-07  5:40 Kiril Vidimce
2001-12-07  5:58 ` Jeffrey H. Ingber

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=20020206162909.GA68254@compsoc.man.ac.uk \
    --to=movement@marcelothewonderpenguin.com \
    --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