mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Henderson <rth@twiddle.net>
To: Matthew Wilcox <willy@infradead.org>, Ingo Molnar <mingo@kernel.org>
Cc: Waiman Long <longman@redhat.com>,
	x86@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Use named address spaces for percpu data
Date: Wed, 12 Sep 2018 08:08:01 -0700	[thread overview]
Message-ID: <988cf77c-e0cc-25fb-dcd6-945e6f2ba65e@twiddle.net> (raw)
In-Reply-To: <20180912144442.29271-1-willy@infradead.org>

On 09/12/2018 07:44 AM, Matthew Wilcox wrote:
> rth wrote a patch back in 2016 that uses gcc's address space machinery
> to improve code generation for percpu accesses.  Ingo asked for some
> minor changes to be made, but Richard didn't respond.  While looking at
> something related, I came across them, and asked Richard's permission
> to resurrect and resend the patch, with the changes Ingo asked for at
> the time.
> 
> The important information about why we want these patch is in 1/2.
> 
> Richard Henderson (2):
>   x86: Use named address spaces in asm/percpu.h
>   x86: Enable named address spaces for percpu data
> 
>  arch/x86/include/asm/percpu.h | 147 ++++++++++++++++++++--------------
>  1 file changed, 88 insertions(+), 59 deletions(-)

Thanks for resurrecting this, Willy.  I'd totally forgotten about it.
The adjustments you made look fine.


r~

  parent reply	other threads:[~2018-09-12 15:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-12 14:44 Matthew Wilcox
2018-09-12 14:44 ` [PATCH 1/2] x86: Use named address spaces in asm/percpu.h Matthew Wilcox
2018-09-12 14:44 ` [PATCH 2/2] x86: Enable named address spaces for percpu data Matthew Wilcox
2018-09-12 15:08 ` Richard Henderson [this message]
2018-09-12 21:06   ` [PATCH 0/2] Use " Ingo Molnar
2018-09-12 21:08     ` Ingo Molnar

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=988cf77c-e0cc-25fb-dcd6-945e6f2ba65e@twiddle.net \
    --to=rth@twiddle.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=longman@redhat.com \
    --cc=mingo@kernel.org \
    --cc=willy@infradead.org \
    --cc=x86@kernel.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
Powered by JetHome