All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ingo Molnar <mingo@elte.hu>, Jens Axboe <jens.axboe@oracle.com>,
	Andi Kleen <andi@firstfloor.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: x86: Is there still value in having a special tlb flush IPI vector?
Date: Tue, 29 Jul 2008 04:12:15 +0200	[thread overview]
Message-ID: <20080729021215.GG30344@one.firstfloor.org> (raw)
In-Reply-To: <488E5455.6010901@goop.org>

On Mon, Jul 28, 2008 at 04:20:53PM -0700, Jeremy Fitzhardinge wrote:
> Resend to cc: Andi on an address which actually works.
> 
> Jeremy Fitzhardinge wrote:
> >Now that normal smp_function_call is no longer an enormous bottleneck, 

Hmm? It still uses a global lock at least as of current git tree.

-Andi

  reply	other threads:[~2008-07-29  2:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-28 23:16 x86: Is there still value in having a special tlb flush IPI vector? Jeremy Fitzhardinge
2008-07-28 23:20 ` Jeremy Fitzhardinge
2008-07-29  2:12   ` Andi Kleen [this message]
2008-07-29  6:29     ` Jeremy Fitzhardinge
2008-07-29 12:02       ` Andi Kleen
2008-07-29 14:46         ` Jeremy Fitzhardinge
2008-07-29 14:58           ` Andi Kleen
2008-07-28 23:34 ` Ingo Molnar
2008-07-29  4:30   ` Nick Piggin
2008-07-29  6:19     ` Jeremy Fitzhardinge
2008-07-29  9:47       ` Nick Piggin
2008-07-29  9:54     ` Peter Zijlstra
2008-07-29 10:00       ` Nick Piggin
2008-07-29 10:04         ` Peter Zijlstra
2008-07-29 10:17           ` Nick Piggin
2008-07-29 10:23             ` Peter Zijlstra
2008-07-29 10:45         ` Peter Zijlstra
2008-07-31 16:48           ` Ingo Molnar
2008-08-01  1:32             ` Nick Piggin
2008-07-31 17:48           ` Jeremy Fitzhardinge
2008-07-31 20:57             ` Ingo Molnar
2008-07-31 21:15               ` Peter Zijlstra

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=20080729021215.GG30344@one.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=jens.axboe@oracle.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.