Hi,
On 18/11/16 at 09:52 +0100, Lars Tangvald wrote:
> Could you try setting /proc/sys/fs/aio-max-nr in your build environment
> (64-core machine) to a high number like 40 (I'm guessing it's set to the
> default 65536), then building with my patch and see if that clears up
> everything?
On Mon, Nov 14, 2016 at 12:31:43PM +0100, Lucas Nussbaum wrote:
> On 14/11/16 at 02:47 -0800, Lars Tangvald wrote:
> > I got it backwards, then :)
> > A high number of cores might cause this if fs.aio-max-nr is set low (cat
> > /proc/sys/fs/aio-max-nr | aio-nr), or rather, too low for the the
>
2 matches
Mail list logo
