Re: [PATCH 1/1] x86: Convert cpuinfo_x86 array to a per_cpu array v2

On Thu, 20 Sep 2007 14:30:05 -0700
[email protected] wrote:

> cpu_data is currently an array defined using NR_CPUS. This means that
> we overallocate since we will rarely really use maximum configured cpus.
> When NR_CPU count is raised to 4096 the size of cpu_data becomes
> 3,145,728 bytes.

This has at least three quite obvious and careless compilation errors.

Please at least compile the code after you've altered it.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• Follow-Ups:
  • Re: [PATCH 1/1] x86: Convert cpuinfo_x86 array to a per_cpu array v2
    • From: Mike Travis <[email protected]>

• References:
  • [PATCH 0/1] x86: Reduce Memory Usage for large CPU count systems v2
    • From: [email protected]
  • [PATCH 1/1] x86: Convert cpuinfo_x86 array to a per_cpu array v2
    • From: [email protected]

• Prev by Date: Re: [PATCH] [4/50] x86: add cpu codenames for Kconfig.cpu
• Next by Date: Re: [PATCH] [20/45] x86_64: Use 8 byte stack alignment when possible
• Previous by thread: [PATCH 1/1] x86: Convert cpuinfo_x86 array to a per_cpu array v2
• Next by thread: Re: [PATCH 1/1] x86: Convert cpuinfo_x86 array to a per_cpu array v2
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]