public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Zwane Mwaikambo <zwane@linuxpower.ca>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH][2.6] Allow x86_64 to reenable interrupts on contention
Date: Tue, 27 Jul 2004 13:26:38 +0200	[thread overview]
Message-ID: <20040727132638.7d26e825.ak@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.58.0407270432470.23989@montezuma.fsmlabs.com>

On Tue, 27 Jul 2004 05:29:10 -0400 (EDT)
Zwane Mwaikambo <zwane@linuxpower.ca> wrote:

> This is a follow up to the previous patches for ia64 and i386, it will
> allow x86_64 to reenable interrupts during contested locks depending on
> previous interrupt enable status. It has been runtime and compile tested
> on UP and 2x SMP Linux-tiny/x86_64.

This will likely increase code size. Do you have numbers by how much? And is it 
really worth it?

-Andi


  reply	other threads:[~2004-07-27 11:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27  9:29 [PATCH][2.6] Allow x86_64 to reenable interrupts on contention Zwane Mwaikambo
2004-07-27 11:26 ` Andi Kleen [this message]
2004-07-27 14:31   ` Zwane Mwaikambo
2004-07-27 15:37     ` Andi Kleen
2004-07-27 16:36       ` Ricky Beam
2004-07-28  8:47         ` Paul Jackson
2004-07-28  1:38       ` Zwane Mwaikambo
2004-07-27 19:01     ` Andrew Morton
2004-07-28  0:14       ` William Lee Irwin III
2004-07-28  0:35         ` Keith Owens
2004-07-28  0:40           ` William Lee Irwin III
2004-07-28  1:48             ` Keith Owens
2004-07-28  2:21               ` William Lee Irwin III
2004-07-28  2:24                 ` David S. Miller
2004-07-28  8:20                   ` William Lee Irwin III
2004-07-28  1:30           ` Zwane Mwaikambo

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=20040727132638.7d26e825.ak@suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zwane@linuxpower.ca \
    /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