From: Davidlohr Bueso <dave@stgolabs.net>
To: Raghavendra K T <raghavendra.kt@amd.com>
Cc: AneeshKumar.KizhakeVeetil@arm.com, Hasan.Maruf@amd.com,
Michael.Day@amd.com, akpm@linux-foundation.org, bharata@amd.com,
dave.hansen@intel.com, david@redhat.com,
dongjoo.linux.dev@gmail.com, feng.tang@intel.com,
gourry@gourry.net, hannes@cmpxchg.org, honggyu.kim@sk.com,
hughd@google.com, jhubbard@nvidia.com, jon.grimm@amd.com,
k.shutemov@gmail.com, kbusch@meta.com, kmanaouil.dev@gmail.com,
leesuyeon0506@gmail.com, leillc@google.com,
liam.howlett@oracle.com, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, mgorman@techsingularity.net,
mingo@redhat.com, nadav.amit@gmail.com, nphamcs@gmail.com,
peterz@infradead.org, riel@surriel.com, rientjes@google.com,
rppt@kernel.org, santosh.shukla@amd.com, shivankg@amd.com,
shy828301@gmail.com, sj@kernel.org, vbabka@suse.cz,
weixugc@google.com, willy@infradead.org,
ying.huang@linux.alibaba.com, ziy@nvidia.com,
Jonathan.Cameron@huawei.com, alok.rathore@samsung.com
Subject: Re: [RFC PATCH V1 00/13] mm: slowtier page promotion based on PTE A bit
Date: Fri, 21 Mar 2025 13:35:55 -0700 [thread overview]
Message-ID: <20250321203555.4n6byk6vmnkmpewi@offworld> (raw)
In-Reply-To: <d0aedf71-047b-4ee4-9175-a67708a389de@amd.com>
On Fri, 21 Mar 2025, Raghavendra K T wrote:
>>But a longer running/ more memory workload may make more difference.
>>I will comeback with that number.
>
> base NUMAB=2 Patched NUMAB=0
> time in sec time in sec
>===================================================
>8G: 134.33 (0.19) 119.88 ( 0.25)
>16G: 292.24 (0.60) 325.06 (11.11)
>32G: 585.06 (0.24) 546.15 ( 0.50)
>64G: 1278.98 (0.27) 1221.41 ( 1.54)
>
>We can see that numbers have not changed much between NUMAB=1 NUMAB=0 in
>patched case.
Thanks. Since this might vary across workloads, another important metric
here is numa hit/misses statistics.
fyi I have also been trying this series to get some numbers as well, but
noticed overnight things went south (so no chance before LSFMM):
[ 464.026917] watchdog: BUG: soft lockup - CPU#108 stuck for 52s! [kmmscand:934]
[ 464.026924] Modules linked in: ...
[ 464.027098] CPU: 108 UID: 0 PID: 934 Comm: kmmscand Tainted: G L 6.14.0-rc6-kmmscand+ #4
[ 464.027105] Tainted: [L]=SOFTLOCKUP
[ 464.027107] Hardware name: Supermicro SSG-121E-NE3X12R/X13DSF-A, BIOS 2.1 01/29/2024
[ 464.027109] RIP: 0010:pmd_off+ 0x58/0xd0
[ 464.027124] Code: 83 e9 01 48 21 f1 48 c1 e1 03 48 89 f8 0f 1f 00 48 23 05 fb c7 fd 00 48 03 0d 0c b9 fb 00 48 25 00 f0 ff ff 48 01 c8 48 8b 38 <48> 89 f8 0f 1f 00 48 8b 0d db c7 fd 00 48 21 c1 48 89 d0 48 c1 e8
[ 464.027128] RSP: 0018:ff71a0dc1b05bbc8 EFLAGS: 00000286
[ 464.027133] RAX: ff3b028e421c17f0 RBX: ffc90cb8322e5e00 RCX: ff3b020d400007f0
[ 464.027136] RDX: 00007f1393978000 RSI: 00000000000000fe RDI: 000000b9726b0067
[ 464.027139] RBP: ff3b02f5d05babc0 R08: 00007f9c5653f000 R09: ffc90cb8322e0001
[ 464.027141] R10: 0000000000000000 R11: ff3b028dd339420c R12: 00007f1393978000
[ 464.027144] R13: ff3b028dded9cbb0 R14: ffc90cb8322e0000 R15: ffffffffb9a0a4c0
[ 464.027146] FS: 0000000000000000(0000) GS:ff3b030bbf400000(0000) knlGS:0000000000000000
[ 464.027150] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 464.027153] CR2: 0000564713088f19 CR3: 000000fb40822006 CR4: 0000000000773ef0
[ 464.027157] DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
[ 464.027159] DR3: 0000000000000000 DR6: 00000000fffe07f0 DR7: 0000000000000400
[ 464.027162] PKRU: 55555554
[ 464.027163] Call Trace:
[ 464.027166] <IRQ>
[ 464.027170] ? watchdog_timer_fn+0x21b/0x2a0
[ 464.027180] ? __pfx_watchdog_timer_fn+0x10/0x10
[ 464.027186] ? __hrtimer_run_queues+0x10f/0x2a0
[ 464.027193] ? hrtimer_interrupt+0xfb/0x240
[ 464.027199] ? __sysvec_apic_timer_interrupt+0x4e/0x110
[ 464.027208] ? sysvec_apic_timer_interrupt+0x68/0x90
[ 464.027219] </IRQ>
[ 464.027221] <TASK>
[ 464.027222] ? asm_sysvec_apic_timer_interrupt+0x16/0x20
[ 464.027236] ? pmd_off+0x58/0xd0
[ 464.027243] hot_vma_idle_pte_entry+0x151/0x500
[ 464.027253] walk_pte_range_inner+0xbe/0x100
[ 464.027260] ? __pte_offset_map_lock+0x9a/0x110
[ 464.027267] walk_pgd_range+0x8f0/0xbb0
[ 464.027271] ? __pfx_hot_vma_idle_pte_entry+0x10/0x10
[ 464.027282] __walk_page_range+0x71/0x1d0
[ 464.027287] ? prepare_to_wait_event+0x53/0x180
[ 464.027294] walk_page_vma+0x98/0xf0
[ 464.027300] kmmscand+0x2aa/0x8d0
[ 464.027310] ? __pfx_kmmscand+0x10/0x10
[ 464.027318] kthread+0xea/0x230
[ 464.027326] ? finish_task_switch.isra.0+0x88/0x2d0
[ 464.027335] ? __pfx_kthread+0x10/0x10
[ 464.027341] ret_from_fork+0x2d/0x50
[ 464.027350] ? __pfx_kthread+0x10/0x10
[ 464.027355] ret_from_fork_asm+0x1a/0x30
[ 464.027365] </TASK>
next prev parent reply other threads:[~2025-03-21 20:36 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-19 19:30 Raghavendra K T
2025-03-19 19:30 ` [RFC PATCH V1 01/13] mm: Add kmmscand kernel daemon Raghavendra K T
2025-03-21 16:06 ` Jonathan Cameron
2025-03-24 15:09 ` Raghavendra K T
2025-03-19 19:30 ` [RFC PATCH V1 02/13] mm: Maintain mm_struct list in the system Raghavendra K T
2025-03-19 19:30 ` [RFC PATCH V1 03/13] mm: Scan the mm and create a migration list Raghavendra K T
2025-03-19 19:30 ` [RFC PATCH V1 04/13] mm: Create a separate kernel thread for migration Raghavendra K T
2025-03-21 17:29 ` Jonathan Cameron
2025-03-24 15:17 ` Raghavendra K T
2025-03-19 19:30 ` [RFC PATCH V1 05/13] mm/migration: Migrate accessed folios to toptier node Raghavendra K T
2025-03-19 19:30 ` [RFC PATCH V1 06/13] mm: Add throttling of mm scanning using scan_period Raghavendra K T
2025-03-19 19:30 ` [RFC PATCH V1 07/13] mm: Add throttling of mm scanning using scan_size Raghavendra K T
2025-03-19 19:30 ` [RFC PATCH V1 08/13] mm: Add initial scan delay Raghavendra K T
2025-03-19 19:30 ` [RFC PATCH V1 09/13] mm: Add heuristic to calculate target node Raghavendra K T
2025-03-21 17:42 ` Jonathan Cameron
2025-03-24 16:17 ` Raghavendra K T
2025-03-19 19:30 ` [RFC PATCH V1 10/13] sysfs: Add sysfs support to tune scanning Raghavendra K T
2025-03-19 19:30 ` [RFC PATCH V1 11/13] vmstat: Add vmstat counters Raghavendra K T
2025-03-19 19:30 ` [RFC PATCH V1 12/13] trace/kmmscand: Add tracing of scanning and migration Raghavendra K T
2025-03-19 19:30 ` [RFC PATCH V1 13/13] prctl: Introduce new prctl to control scanning Raghavendra K T
2025-03-19 23:00 ` [RFC PATCH V1 00/13] mm: slowtier page promotion based on PTE A bit Davidlohr Bueso
2025-03-20 8:51 ` Raghavendra K T
2025-03-20 19:11 ` Raghavendra K T
2025-03-21 20:35 ` Davidlohr Bueso [this message]
2025-03-25 6:36 ` Raghavendra K T
2025-03-20 21:50 ` Davidlohr Bueso
2025-03-21 6:48 ` Raghavendra K T
2025-03-21 15:52 ` Jonathan Cameron
[not found] ` <20250321105309.3521-1-hdanton@sina.com>
2025-03-23 18:14 ` [RFC PATCH V1 09/13] mm: Add heuristic to calculate target node Raghavendra K T
[not found] ` <20250324110543.3599-1-hdanton@sina.com>
2025-03-24 14:54 ` Raghavendra K T
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250321203555.4n6byk6vmnkmpewi@offworld \
--to=dave@stgolabs.net \
--cc=AneeshKumar.KizhakeVeetil@arm.com \
--cc=Hasan.Maruf@amd.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=Michael.Day@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alok.rathore@samsung.com \
--cc=bharata@amd.com \
--cc=dave.hansen@intel.com \
--cc=david@redhat.com \
--cc=dongjoo.linux.dev@gmail.com \
--cc=feng.tang@intel.com \
--cc=gourry@gourry.net \
--cc=hannes@cmpxchg.org \
--cc=honggyu.kim@sk.com \
--cc=hughd@google.com \
--cc=jhubbard@nvidia.com \
--cc=jon.grimm@amd.com \
--cc=k.shutemov@gmail.com \
--cc=kbusch@meta.com \
--cc=kmanaouil.dev@gmail.com \
--cc=leesuyeon0506@gmail.com \
--cc=leillc@google.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mingo@redhat.com \
--cc=nadav.amit@gmail.com \
--cc=nphamcs@gmail.com \
--cc=peterz@infradead.org \
--cc=raghavendra.kt@amd.com \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=rppt@kernel.org \
--cc=santosh.shukla@amd.com \
--cc=shivankg@amd.com \
--cc=shy828301@gmail.com \
--cc=sj@kernel.org \
--cc=vbabka@suse.cz \
--cc=weixugc@google.com \
--cc=willy@infradead.org \
--cc=ying.huang@linux.alibaba.com \
--cc=ziy@nvidia.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox