From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Andi Kleen <ak-l3A5Bk7waGM@public.gmane.org>
Cc: Nick Piggin <npiggin-l3A5Bk7waGM@public.gmane.org>,
Ingo Molnar <mingo-X9Un+BFzKDI@public.gmane.org>,
Linux Kernel Mailing List
<linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [rfc][patch] x86-64 new smp_call_function design
Date: Sun, 16 Mar 2008 16:33:37 +0200 [thread overview]
Message-ID: <47DD2FC1.8040106@qumranet.com> (raw)
In-Reply-To: <47C5668C.6040906-l3A5Bk7waGM@public.gmane.org>
Andi Kleen wrote:
>
>>>> 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()
>
kvm is also a heavy user of smp_call_function_mask(); if you run
multiple smp guests you'll see plenty of disjoint smp_call_function_mask()s.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe linux-arch" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Avi Kivity <avi@qumranet.com>
To: Andi Kleen <ak@suse.de>
Cc: Nick Piggin <npiggin@suse.de>, 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: Sun, 16 Mar 2008 16:33:37 +0200 [thread overview]
Message-ID: <47DD2FC1.8040106@qumranet.com> (raw)
Message-ID: <20080316143337.wtlPPDSyFQsHoNZTWF5Z0ittsYqh9EWLi5mSgEcdnog@z> (raw)
In-Reply-To: <47C5668C.6040906@suse.de>
Andi Kleen wrote:
>
>>>> 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()
>
kvm is also a heavy user of smp_call_function_mask(); if you run
multiple smp guests you'll see plenty of disjoint smp_call_function_mask()s.
--
error compiling committee.c: too many arguments to function
next prev parent reply other threads:[~2008-03-16 14:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 12:42 [rfc][patch] x86-64 new smp_call_function design Nick Piggin
2008-02-27 13:04 ` Andi Kleen
2008-02-27 13:07 ` Nick Piggin
2008-02-27 13:33 ` Andi Kleen
[not found] ` <47C5668C.6040906-l3A5Bk7waGM@public.gmane.org>
2008-03-16 14:33 ` Avi Kivity [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=47DD2FC1.8040106@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=ak-l3A5Bk7waGM@public.gmane.org \
--cc=linux-arch-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mingo-X9Un+BFzKDI@public.gmane.org \
--cc=npiggin-l3A5Bk7waGM@public.gmane.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 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.