From: Jiang Liu <jiang.liu@linux.intel.com>
To: Thomas Gleixner <tglx@linutronix.de>,
Daniel J Blueman <daniel@numascale.com>
Cc: Ingo Molnar <mingo@kernel.org>,
Denys Vlasenko <dvlasenk@redhat.com>,
Len Brown <len.brown@intel.com>,
Steffen Persvold <sp@numascale.com>,
linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH v2] x86/apic: Use smaller array for __apicid_to_node[] mapping
Date: Fri, 9 Oct 2015 23:16:54 +0800 [thread overview]
Message-ID: <5617DA66.1040006@linux.intel.com> (raw)
In-Reply-To: <alpine.DEB.2.11.1510091614020.6097@nanos>
On 2015/10/9 22:15, Thomas Gleixner wrote:
> On Mon, 5 Oct 2015, Daniel J Blueman wrote:
>> +struct apicid_to_node {
>> + int apicid;
>> + s16 node;
>> +};
>
> Instead of having this array, why don't you use a radix tree and be
> done with it?
Hi Thomas,
It's in early booting stage and memory allocator isn't ready
yet.
Thanks,
Gerry
next prev parent reply other threads:[~2015-10-09 15:16 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 19:12 [PATCH 1/3] x86/apic: Rename MAX_LOCAL_APIC to MAX_LOCAL_APICID Denys Vlasenko
2015-10-02 19:12 ` [PATCH 2/3] x86/apic: Make apic_version[] smaller Denys Vlasenko
2015-10-02 19:12 ` [PATCH 3/3] x86/apic: Use smaller array for __apicid_to_node[] mapping Denys Vlasenko
2015-10-03 7:44 ` Ingo Molnar
2015-10-03 20:26 ` Denys Vlasenko
2015-10-05 4:32 ` [PATCH v2] " Daniel J Blueman
2015-10-09 14:15 ` Thomas Gleixner
2015-10-09 15:16 ` Jiang Liu [this message]
2015-10-09 20:40 ` Thomas Gleixner
2015-10-09 15:35 ` [PATCH 3/3] " Jiang Liu
2015-10-12 10:21 ` Daniel J Blueman
2015-10-12 10:25 ` Thomas Gleixner
2015-10-13 9:32 ` Jiang Liu
2015-10-13 12:55 ` Thomas Gleixner
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=5617DA66.1040006@linux.intel.com \
--to=jiang.liu@linux.intel.com \
--cc=daniel@numascale.com \
--cc=dvlasenk@redhat.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=sp@numascale.com \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).