LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Nick Piggin <npiggin@suse.de>
Cc: Ingo Molnar <mingo@elte.hu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-arch@vger.kernel.org
Subject: Re: [rfc][patch] x86-64 new smp_call_function design
Date: Wed, 27 Feb 2008 14:33:00 +0100	[thread overview]
Message-ID: <47C5668C.6040906@suse.de> (raw)
In-Reply-To: <20080227130716.GB1340@wotan.suse.de>


> *vmalloc* TLB flushing. 
> 
> void flush_tlb_all(void)
> {
>         on_each_cpu(do_flush_tlb_all, NULL, 1, 1);
> }
> 
> Of course we could use a new vector for it and speed it up a lot more,
> but after my vmalloc improvements I think that would be a waste of a
> vector at this point.

Ah I see sorry. If you want to just speed up vmalloc flushing I think
the easier way would be to just extend the normal TLB flusher for
vmalloc. So alone for this it probably wouldn't be worth it.

But I think it'll be useful for a couple of other things.

>>> As far as I understand, calling a subset of online CPUs that is not all or
>>> one, is used quite infrequently, so this might be OK.
>> With cpusets and isolation etc. it is the normal case.
> 
> Oh really? Coming from what callers?

The isolation work is not merged yet, but it will essentially need
to turn a lot of the _call_function()s into _call_function_mask()

-Andi



  reply	other threads:[~2008-02-27 13:31 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27 12:42 Nick Piggin
2008-02-27 13:04 ` Andi Kleen
2008-02-27 13:07   ` Nick Piggin
2008-02-27 13:33     ` Andi Kleen [this message]
2008-03-16 14:33       ` Avi Kivity
2008-02-27 13:27 ` Ingo Molnar
2008-02-27 13:50   ` Nick Piggin
2008-02-27 15:02     ` Ingo Molnar
2008-02-27 22:14       ` Nick Piggin
2008-02-28  8:45         ` Ingo Molnar
2008-02-28 12:55           ` Andi Kleen

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=47C5668C.6040906@suse.de \
    --to=ak@suse.de \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=npiggin@suse.de \
    --subject='Re: [rfc][patch] x86-64 new smp_call_function design' \
    /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

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).