From: Oleg Nesterov <oleg@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: linux-kernel@vger.kernel.org, travis@sgi.com,
Ingo Molnar <mingo@elte.hu>, Gautham R Shenoy <ego@in.ibm.com>
Subject: Re: [PATCH 6/7] work_on_cpu: use on x86/kernel/cpu/intel_cacheinfo.c
Date: Thu, 23 Oct 2008 18:16:12 +0200 [thread overview]
Message-ID: <20081023161612.GA21008@redhat.com> (raw)
In-Reply-To: <200810240210.31573.rusty@rustcorp.com.au>
On 10/24, Rusty Russell wrote:
>
> Can we use smp_call_function here instead?
I think you are right, smp_call_function_single() should be fine.
But please note I don't really understand this code ;)
Oleg.
prev parent reply other threads:[~2008-10-23 16:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 16:55 [PATCH 6/7] work_on_cpu: use on x86/kernel/cpu/intel_cacheinfo.c Rusty Russell
2008-10-23 9:46 ` Oleg Nesterov
2008-10-23 15:10 ` Rusty Russell
2008-10-23 16:16 ` Oleg Nesterov [this message]
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=20081023161612.GA21008@redhat.com \
--to=oleg@redhat.com \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=rusty@rustcorp.com.au \
--cc=travis@sgi.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