public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Subject: Re: [RFC, patch] i386: vgetcpu()
Date: Tue, 20 Jun 2006 22:57:16 +0200	[thread overview]
Message-ID: <200606202257.16033.ak@suse.de> (raw)
In-Reply-To: <200606201628_MC3-1-C2FA-3586@compuserve.com>

On Tuesday 20 June 2006 22:25, Chuck Ebbert wrote:
> Use the limit field of a GDT entry to store the current CPU
> number for fast userspace access.  This still leaves 12 bits
> free for other information.

Nice trick. Maybe I'll even add that to the x86-64 implementation
if it's fast enough. Do you have numbers?

But it needs to be encapsulated in a wrapper I think. Just exposing
it to user space is the wrong way to do this.

-Andi

  reply	other threads:[~2006-06-20 20:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-20 20:25 [RFC, patch] i386: vgetcpu() Chuck Ebbert
2006-06-20 20:57 ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-06-20 22:40 Chuck Ebbert

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=200606202257.16033.ak@suse.de \
    --to=ak@suse.de \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox