From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [PATCH] brd: Allow ramdisk to be allocated on selected NUMA node To: Adam Manzanares , Jens Axboe Cc: "linux-block@vger.kernel.org" , Mel Gorman , Hannes Reinecke References: <20180614133832.110947-1-hare@suse.de> <08318d74-d81c-29e5-5350-525df96eaacb@kernel.dk> <20180614172954.79965d13@pentland.suse.de> <656e4ab7-7c5c-41af-5596-2e155ffb28e4@kernel.dk> <20180614180937.591bb361@pentland.suse.de> <53893c29-febc-14ff-314d-818ac79aa559@wdc.com> <5f21f241-0ae0-ed7a-6935-3ef6e65d0950@kernel.dk> From: Hannes Reinecke Message-ID: Date: Fri, 15 Jun 2018 08:06:04 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed List-ID: On 06/14/2018 10:53 PM, Adam Manzanares wrote: [ .. ] >>> >>> Then how about a numactl ... dd /dev/ram ... after the modprobe. >> >> Yes of course, or you could do that for every application that ends >> up in the path of the doing IO to it. The point of the option is to >> just make it explicit, and not have to either NUMA pin each task, >> or prefill all possible pages. >> > > Makes sense, I have done some similar benchmarking and had to worry > about NUMA awareness and the numactl + dd approach seemed to work > because I wanted to not take a performance hit for page allocation > during the benchmarking. > > Would anyone be interested in forcing the allocations to occur during > module initialization? > YES. Cheers, Hannes