netdev - Re: [net-next-2.6 PATCH 2/5] ixgbe: Make descriptor ring allocations NUMA-aware

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 08 Jan 2010 00:31:22 -0800 (PST)
From:	David Miller <davem@...emloft.net>
To:	peter.p.waskiewicz.jr@...el.com
Cc:	jeffrey.t.kirsher@...el.com, netdev@...r.kernel.org,
	gospo@...hat.com
Subject: Re: [net-next-2.6 PATCH 2/5] ixgbe: Make descriptor ring
 allocations NUMA-aware

From: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@...el.com>
Date: Fri, 8 Jan 2010 00:25:26 -0800 (Pacific Standard Time)

> In our hardware (82598 and 82599), the CPU field in the DCA registers is 8 
> bits.
> 
> The reason I truncated this was to fit these values into the 
> first cacheline of the struct.  I also didn't figure we'd see a system 
> that would have 255 NUMA nodes before 10 GbE was something that was on the 
> shelf collecting dust.  :-)

The X86 port supports 9 for "NODES_SHIFT", and up to 4096 cpus.

Even when !MAXSMP, the cpu limit is 512.

Don't make the type ungeneric just because some current piece of
hardware has that limitation.  This is how subtle bugs slip into the
tree, and it makes auditing for such bugs a nightmare.

Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html