From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Hugh Dickins <hugh@veritas.com>, Jack Steiner <steiner@sgi.com>,
Jeremy Fitzhardinge <jeremy@goop.org>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] x86_64: Optimize percpu accesses
Date: Mon, 28 Jul 2008 11:33:12 -0700 [thread overview]
Message-ID: <488E10E8.8070504@sgi.com> (raw)
In-Reply-To: <20080726123819.GC20713@elte.hu>
Ingo Molnar wrote:
> * Mike Travis <travis@sgi.com> wrote:
>
>> This patchset provides the following:
>>
>> * x86_64: Cleanup setup_percpu by fixing some minor potential
>> problems as well as add some debugging aids.
>>
>> * x86_64: Rebase per cpu variables to zero
>>
>> Rebase per cpu variables to zero in preparation for the following
>> patch to fold the pda into the per cpu area.
>>
>> * x86_64: Fold pda into per cpu area
>>
>> Declare the pda as a per cpu variable. This will allow the per cpu
>> variables to be accessible on the x86_64 using %gs as the base of
>> the percpu areas for each cpu:
>>
>> %gs:per_cpu_xxxx
>>
>> * x86_64: Reference zero-based percpu variables offset from gs
>>
>> Actually implement the above operation for __get_cpu_var() and
>> __put_cpu_var(). Since this is now a single instruction, we
>> can remove the non-preemptible versions of x86_read_percpu()
>> and x86_write_percpu().
>>
>> Note that the following changes are NOT in this patchset as the plan now
>> seems to be that the common (to x86) variables that are in the pda should
>> be made individual per cpu variables, leaving only the stack canary in place.
>>
>> * x86_64: Replace cpu_pda ops with percpu ops
>> * x86_64: Replace xxx_pda() operations with x86_xxx_percpu().
>> * x86_64: Remove xxx_pda() operations
>> * x86_64: Remove cpu_pda() macro
>>
>> Based on linux-2.6.tip/master.
>
> i've added these patches to tip/x86/percpu-zerobased, but not yet merged
> into tip/master. I've made it -git based - does this patchset have any
> functional dependencies on other patches?
>
> Ingo
I think the other patches have been in place for a while. This was actually
patch 3 of about 20 that finalized with the CPU_ALLOC changes. In my tree
the 2 prior to this one are:
b3a0cb456d848e10b2f7b371ba05e44f1384520a
Subject: Zero based percpu: Infrastructure to rebase the per cpu area to zero
d3794979a8a80c222ce9d016a6dfc4bed36965d0
Subject: x86: Extend percpu ops to 64 bit
Thanks,
Mike
next prev parent reply other threads:[~2008-07-28 18:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-25 21:11 [PATCH 0/4] x86_64: Optimize percpu accesses Mike Travis
2008-07-25 21:11 ` [PATCH 1/4] x86_64: Cleanup early setup_percpu references Mike Travis
2008-07-25 21:11 ` [PATCH 2/4] x86_64: Base percpu variables at zero Mike Travis
2008-07-25 21:11 ` [PATCH 3/4] x86_64: Fold pda into per cpu area Mike Travis
2008-07-25 21:11 ` [PATCH 4/4] x86_64: Reference zero-based percpu variables offset from gs Mike Travis
2008-07-25 23:26 ` [PATCH 0/4] x86_64: Optimize percpu accesses Jeremy Fitzhardinge
2008-07-26 0:27 ` Mike Travis
2008-07-26 0:30 ` Jeremy Fitzhardinge
2008-07-26 12:38 ` Ingo Molnar
2008-07-28 18:33 ` Mike Travis [this message]
2008-07-28 15:52 ` [crash] " Ingo Molnar
2008-07-28 19:39 ` Mike Travis
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=488E10E8.8070504@sgi.com \
--to=travis@sgi.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=hpa@zytor.com \
--cc=hugh@veritas.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=steiner@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