The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Mike Travis <travis@sgi.com>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Ingo Molnar <mingo@elte.hu>,
	Rusty Russell <rusty@rustcorp.com.au>
Subject: Re: Further percpu/pda unification?
Date: Mon, 02 Jun 2008 08:28:35 -0700	[thread overview]
Message-ID: <484411A3.2000205@sgi.com> (raw)
In-Reply-To: <48440264.5060506@goop.org>

Jeremy Fitzhardinge wrote:
> I notice that there's now a unified asm-x86/percpu.h, and the pda is now
> a per-cpu variable.  But I also see that most of the stuff in percpu.h
> is 32-bit only: all the accessor macros, x86_read/write_percpu, etc.  Is
> there some reason why that can't be made common, or is it just that
> nobody has got around to it yet?
> 
> Thanks,
>    J

Hi Jeremy,

I'll have a further unification patch shortly, just doing final testing now.

Thanks,
Mike

  reply	other threads:[~2008-06-02 15:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-02 14:23 Further percpu/pda unification? Jeremy Fitzhardinge
2008-06-02 15:28 ` Mike Travis [this message]
2008-06-02 15:59   ` Jeremy Fitzhardinge

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=484411A3.2000205@sgi.com \
    --to=travis@sgi.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=rusty@rustcorp.com.au \
    /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