From: Andi Kleen <ak@suse.de>
To: Eric Dumazet <dada1@cosmosbay.com>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [NUMA , x86_64] Why memnode_shift is chosen with the lowest possible value ?
Date: Thu, 29 Sep 2005 15:43:37 +0200 [thread overview]
Message-ID: <20050929134337.GF2720@wotan.suse.de> (raw)
In-Reply-To: <433BEED6.6000008@cosmosbay.com>
> Using memnode_shift=33 would access only 2 bytes from this memnodemap[],
> touching fewer cache lines (well , one cache line). kfree() and friends
> would be slightly faster, at least cache friendly.
Agreed. Please send a patch.
>
> Another question is :
>
> Could we add in pda (struct x8664_pda) the node of the cpu ?
>
> We currently do :
>
> #define numa_node_id() (cpu_to_node(raw_smp_processor_id()))
>
> Instead of reading the processor_id from pda, then access cpu_to_node[], we
> could directly get this information from pda.
>
> #if defined(CONFIG_NUMA)
> static inline __attribute_pure__ int numa_node_id() { return
> read_pda(node);}
> #else
> #define numa_node_id() 0
> #endif
Should be fine too. Please send a patch for that too.
-Andi
next prev parent reply other threads:[~2005-09-29 13:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-28 20:25 [PATCH 0/3] Demand faulting for huge pages Adam Litke
2005-09-28 20:31 ` [PATCH 1/3 htlb-get_user_pages] " Adam Litke
2005-09-28 20:32 ` [PATCH 2/3 htlb-fault] " Adam Litke
2005-09-29 6:09 ` Andrew Morton
2005-09-29 6:10 ` Andrew Morton
2005-09-28 20:33 ` [PATCH 3/3 htlb-acct] " Adam Litke
2005-09-29 6:20 ` Andrew Morton
2005-09-29 9:45 ` Andi Kleen
2005-09-29 13:40 ` [NUMA , x86_64] Why memnode_shift is chosen with the lowest possible value ? Eric Dumazet
2005-09-29 13:43 ` Andi Kleen [this message]
2005-09-29 16:59 ` Eric Dumazet
2005-09-30 9:09 ` Eric Dumazet
2005-10-04 17:13 ` Andi Kleen
2005-10-04 21:12 ` Eric Dumazet
2005-09-29 13:32 ` [PATCH 0/3] Demand faulting for huge pages Hugh Dickins
2005-10-06 15:22 ` Adam Litke
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=20050929134337.GF2720@wotan.suse.de \
--to=ak@suse.de \
--cc=dada1@cosmosbay.com \
--cc=linux-kernel@vger.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