linux-kernel - Re: Hard and soft lockups with FIO and LTP runs on a large system

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]

Message-Id: <20240717111510.1260-1-hdanton@sina.com>
Date: Wed, 17 Jul 2024 19:15:10 +0800
From: Hillf Danton <hdanton@...a.com>
To: Bharata B Rao <bharata@....com>
Cc: Vlastimil Babka <vbabka@...e.cz>,
	Yu Zhao <yuzhao@...gle.com>,
	linux-mm@...ck.org,
	linux-kernel@...r.kernel.org,
	willy@...radead.org,
	Mel Gorman <mgorman@...e.de>
Subject: Re: Hard and soft lockups with FIO and LTP runs on a large system

On Wed, 17 Jul 2024 16:20:04 +0530 Bharata B Rao <bharata@....com>
> On 17-Jul-24 3:07 PM, Vlastimil Babka wrote:
> > 
> > It seems weird to me to see anything that would require ZONE_DMA allocation
> > on a modern system. Do you know where it comes from?
> 
> We measured the lruvec spinlock start, end and hold
> time(htime) using sched_clock(), along with a BUG() if the hold time was
> more than 10s. The below case shows that lruvec spin lock was held for ~25s.
>
What is more unusual could be observed perhaps with your hardware config but
with 386MiB RAM assigned to each node, the so called tight memory but not
extremely tight.