linux-kernel - Re: [PATCH 1/4] try parent numa_node at first before using default

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:	Mon, 09 Jul 2007 18:03:43 -0700
From:	Yinghai Lu <Yinghai.Lu@....COM>
To:	Greg KH <greg@...ah.com>
Cc:	akpm@...ux-foundation.org, ak@...e.de, clameter@....com,
	rientjes@...gle.com,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 1/4] try parent numa_node at first before using default

Greg KH wrote:
> On Tue, Jul 03, 2007 at 05:31:02PM -0700, Yinghai Lu wrote:
>> [PATCH 1/4] try parent numa_node at first before using default
>>
> 
> What is this going to give us?
you can use dev_to_node(netdev->dev) or dev_to_node(usb_device->dev) directly, and don't need to go to find pci_device up to get numa_node.
> 
> Doesn't it mean that all devices will end up on the same node?
yes.
For x86_64, devices under node1 will have 1, and device under node0 will all have 0.

current only pci_dev->dev.numa_node is used.

YH


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/