mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ravikiran G Thirumalai <kiran@scalex86.org>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Andi Kleen <ak@suse.de>, Andrew Morton <akpm@osdl.org>,
	linux-kernel@vger.kernel.org, discuss@x86-64.org,
	shai@scalex86.org
Subject: Re: [discuss] Re: [patch 3/3] x86_64: Node local PDA -- allocate node local memory for pda
Date: Fri, 2 Dec 2005 10:24:27 -0800	[thread overview]
Message-ID: <20051202182427.GA3727@localhost.localdomain> (raw)
In-Reply-To: <43900BE3.5080000@cosmosbay.com>

On Fri, Dec 02, 2005 at 09:54:59AM +0100, Eric Dumazet wrote:
> Ravikiran G Thirumalai a écrit :
> >Patch uses a static PDA array early at boot and reallocates processor PDA
> >with node local memory when kmalloc is ready, just before pda_init.
> >The boot_cpu_pda is needed sice the cpu_pda is used even before pda_init 
> >for
> >that cpu is called (to set the static per-cpu areas offset table etc)
> >
> 
> That sounds great.
> 
> I have only have one suggestion : If kernel is not NUMA, then maybe we 
> should avoid one indirection to get the pda, and avoid some code too.
>

Sure, but there is no extra indirection with the fastpath routines like
read_pda, write_pda and friends with the current patch.  
Places where cpu_pda[] is accessed by the array name are not really
important -- except for the static per_cpu_offset of another cpu.  But
still it might be worth it (considering that people use 
per_cpu(var, smp_processor_id()), instead of __get_cpu_var in many places).  
I will incorporate this.

Thanks,
Kiran

  reply	other threads:[~2005-12-02 18:24 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-02  8:10 [patch 1/3] x86_64: Node local PDA -- early cpu_to_node Ravikiran G Thirumalai
2005-12-02  8:16 ` [patch 2/3] x86_64: Node local PDA -- Use macros to access cpu_pda Ravikiran G Thirumalai
2005-12-02  8:23 ` [patch 3/3] x86_64: Node local PDA -- allocate node local memory for pda Ravikiran G Thirumalai
2005-12-02  8:54   ` Eric Dumazet
2005-12-02 18:24     ` Ravikiran G Thirumalai [this message]
2005-12-02  9:05   ` Andrew Morton
2005-12-02 10:36     ` [RFC] NUMA aware kthread_create() ? Eric Dumazet
2005-12-02 12:32       ` [discuss] " Andi Kleen
2005-12-02 11:47   ` [patch 3/3] x86_64: Node local PDA -- allocate node local memory for pda Andi Kleen
2005-12-02 20:02     ` Ravikiran G Thirumalai
2005-12-02 22:41       ` Andi Kleen
2005-12-02 11:43 ` [patch 1/3] x86_64: Node local PDA -- early cpu_to_node Andi Kleen
2005-12-02 22:51   ` [discuss] " Ravikiran G Thirumalai
2005-12-02 23:02     ` Andi Kleen
2005-12-02 23:43       ` Ravikiran G Thirumalai
2005-12-02 23:48         ` Andi Kleen

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=20051202182427.GA3727@localhost.localdomain \
    --to=kiran@scalex86.org \
    --cc=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=dada1@cosmosbay.com \
    --cc=discuss@x86-64.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shai@scalex86.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