From: Andi Kleen <ak@suse.de>
To: "Martin J. Bligh" <mbligh@google.com>
Cc: Chuck Ebbert <76306.1226@compuserve.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Rohit Seth <rohitseth@google.com>, Andrew Morton <akpm@osdl.org>,
Ingo Molnar <mingo@elte.hu>
Subject: Re: [RFC, patch] i386: vgetcpu() for NUMA, take 2
Date: Sun, 25 Jun 2006 17:19:35 +0200 [thread overview]
Message-ID: <200606251719.35479.ak@suse.de> (raw)
In-Reply-To: <449D5C21.5060600@google.com>
> What was the point of returning wrong info to userspace really quickly?
Read the long rationale in my original vgetcpu() post.
-Andi
prev parent reply other threads:[~2006-06-25 15:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-24 8:23 [RFC, patch] i386: vgetcpu() for NUMA, take 2 Chuck Ebbert
2006-06-24 15:37 ` Martin J. Bligh
2006-06-25 15:19 ` Andi Kleen [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=200606251719.35479.ak@suse.de \
--to=ak@suse.de \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=rohitseth@google.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