linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rusty Russell <rusty@rustcorp.com.au>
To: Dave Hansen <haveblue@us.ibm.com>
Cc: akpm@zip.com.au, linux-kernel@vger.kernel.org,
	torvalds@transmeta.com, mingo@elte.hu,
	Benjamin LaHaise <bcrl@redhat.com>
Subject: Re: [PATCH]  4KB stack + irq stack for x86
Date: Wed, 18 Sep 2002 13:22:27 +1000	[thread overview]
Message-ID: <20020918132227.6a323aff.rusty@rustcorp.com.au> (raw)
In-Reply-To: <3D7FCB09.7050105@us.ibm.com>

On Wed, 11 Sep 2002 16:00:25 -0700
Dave Hansen <haveblue@us.ibm.com> wrote:

> This is a resync of the last patch for 2.5.34 that resulted from this discussion 
> (not the original patch):
> http://lwn.net/Articles/1642/
> The only change was readding the reference to task_info in the beginning of 
> common_interrupt.  It had been dropped when we stopped messing with 
> preempt_count there.
> 
> I've beaten this thing with my normal array of Specweb tests and it is behaving 
> so far.  I've booted on an 8-way with and without SMP.

I'd really like to see this in 2.5, if only to make massively threaded
programs using Ingo's pthreads mods even more viable, and show up those people
who think userspace threading libraries are a good idea 8)

Rusty.
-- 
   there are those who do and those who hang on and you don't see too
   many doers quoting their contemporaries.  -- Larry McVoy

  reply	other threads:[~2002-09-18  3:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-11 23:00 [PATCH] 4KB stack + irq stack for x86 Dave Hansen
2002-09-18  3:22 ` Rusty Russell [this message]
2002-10-04 20:00 Dave Hansen
2002-10-04 20:12 ` Dave Hansen

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=20020918132227.6a323aff.rusty@rustcorp.com.au \
    --to=rusty@rustcorp.com.au \
    --cc=akpm@zip.com.au \
    --cc=bcrl@redhat.com \
    --cc=haveblue@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=torvalds@transmeta.com \
    /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;
as well as URLs for NNTP newsgroup(s).