From: Benjamin LaHaise <bcrl@redhat.com>
To: Andreas Haumer <andreas@xss.co.at>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Linux-2.2.20 SMP & Asus CUR-DLS: "stuck on TLB IPI wait (CPU#3)"
Date: Sat, 12 Jan 2002 18:14:12 -0500 [thread overview]
Message-ID: <20020112181412.B31913@redhat.com> (raw)
In-Reply-To: <3C40B268.C2B87902@xss.co.at> <20020112173430.A31913@redhat.com> <3C40C066.CF147D02@xss.co.at>
In-Reply-To: <3C40C066.CF147D02@xss.co.at>; from andreas@xss.co.at on Sun, Jan 13, 2002 at 12:01:58AM +0100
On Sun, Jan 13, 2002 at 12:01:58AM +0100, Andreas Haumer wrote:
> Aha!
>
> Anyone working on backporting it to 2.2.21?
> Alan?
That's unlikely: the improvements in smp locking are what 2.4 was all about,
so "backporting" them is basically reinventing 2.4.
-ben
next prev parent reply other threads:[~2002-01-12 23:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 22:02 Linux-2.2.20 SMP & Asus CUR-DLS: "stuck on TLB IPI wait (CPU#3)" Andreas Haumer
2002-01-12 22:34 ` Benjamin LaHaise
2002-01-12 23:01 ` Andreas Haumer
2002-01-12 23:14 ` Benjamin LaHaise [this message]
2002-01-13 1:39 ` Alan Cox
2002-01-13 1:45 ` Reid Hekman
2002-01-13 2:01 ` Alan Cox
2002-01-13 11:45 ` Andreas Haumer
2002-01-13 15:39 ` Alan Cox
2002-01-13 15:55 ` Andreas Haumer
2002-01-13 16:26 ` Andreas Haumer
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=20020112181412.B31913@redhat.com \
--to=bcrl@redhat.com \
--cc=andreas@xss.co.at \
--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