linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Travis <travis@sgi.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Andi Kleen <ak@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Christoph Lameter <clameter@sgi.com>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Rusty Russell <rusty@rustcorp.com.au>,
	tglx@linutronix.de, mingo@redhat.com,
	"H. Peter Anvin" <hpa@zytor.com>
Subject: Re: [PATCH 05/10] x86_64: Use generic percpu
Date: Mon, 31 Dec 2007 08:21:01 -0800	[thread overview]
Message-ID: <477916ED.8010602@sgi.com> (raw)
In-Reply-To: <20071230141829.GA28415@elte.hu>

Ingo Molnar wrote:
> * Mike Travis <travis@sgi.com> wrote:
> 
>>> Also for such changes .text size comparisons before/after are a good 
>>> idea.
>> x86_64-defconfig:
>>
>> pre-percpu                          post-percpu
>>       159373 .init.text                       +3 .init.text
>>      1411137 .rodata                          +8 .rodata
>>      3629056 .text                           +48 .text
>>      7057383 Total                           +59 Total
> 
> ok, that looks like really minimal impact, so i'm in favor of merging 
> this into arch/x86 - and the unification it does later on is nice too.
> 
> to get more test feedback: what would be the best way to get this tested 
> in x86.git in a standalone way? Can i just pick up these 10 patches and 
> remove all the non-x86 arch changes, and expect it to work - or are the 
> other percpu preparatory/cleanup patches in -mm needed too?
> 
> 	Ingo

I've tested some x86_64 configs but the UP model is currently broken so I
haven't been able to test that. (the "fs/nfs/super.c" build problem with
TASK_NORMAL and TASK_UNINTERRUPTIBLE undefined.)

Thanks,
Mike

  reply	other threads:[~2007-12-31 16:21 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-28  0:10 [PATCH 00/10] percpu: Per cpu code simplification V2 travis
2007-12-28  0:10 ` [PATCH 01/10] percpu: Use a kconfig variable to signal arch specific percpu setup travis
2007-12-28  0:15   ` David Miller
2007-12-28  0:10 ` [PATCH 02/10] percpu: Move arch XX_PER_CPU_XX definitions into linux/percpu.h travis
2007-12-28  0:16   ` David Miller
2007-12-28  0:10 ` [PATCH 03/10] percpu: Make the asm-generic/percpu.h more "generic" travis
2007-12-28  0:18   ` David Miller
2007-12-28  0:10 ` [PATCH 04/10] x86_32: Use generic percpu.h travis
2007-12-28  0:10 ` [PATCH 05/10] x86_64: Use generic percpu travis
2007-12-28 12:54   ` Andi Kleen
2007-12-28 22:05     ` Mike Travis
2007-12-29  1:55       ` Andi Kleen
2007-12-31 16:19         ` Mike Travis
2008-01-02 20:58         ` Christoph Lameter
2007-12-30 14:18       ` Ingo Molnar
2007-12-31 16:21         ` Mike Travis [this message]
2007-12-31 17:10           ` Mike Travis
2008-01-01 19:17             ` Ingo Molnar
2008-01-02 21:04               ` Christoph Lameter
2008-01-02 21:33                 ` Ingo Molnar
2008-01-02 20:59         ` Christoph Lameter
2008-01-02 20:55     ` Christoph Lameter
2007-12-28  0:10 ` [PATCH 06/10] s390: " travis
2007-12-28  0:10 ` [PATCH 07/10] Powerpc: Use generic per cpu travis
  -- strict thread matches above, loose matches on Subject: below --
2008-01-08 21:10 [PATCH 00/10] percpu: Per cpu code simplification V4 travis
2008-01-08 21:10 ` [PATCH 05/10] x86_64: Use generic percpu travis
2008-01-08  2:11 [PATCH 00/10] percpu: Per cpu code simplification V3 travis
2008-01-08  2:11 ` [PATCH 05/10] x86_64: Use generic percpu travis
2007-12-28  0:16 [PATCH 00/10] percpu: Per cpu code simplification V2 travis
2007-12-28  0:16 ` [PATCH 05/10] x86_64: Use generic percpu travis
2007-11-28 21:09 [patch 00/10] Per cpu code simplification V2 Christoph Lameter
2007-11-28 21:09 ` [patch 05/10] x86_64: Use generic percpu Christoph Lameter
2007-11-30 11:11   ` 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=477916ED.8010602@sgi.com \
    --to=travis@sgi.com \
    --cc=ak@suse.de \
    --cc=akpm@linux-foundation.org \
    --cc=clameter@sgi.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=mingo@redhat.com \
    --cc=rusty@rustcorp.com.au \
    --cc=tglx@linutronix.de \
    /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;
as well as URLs for NNTP newsgroup(s).