linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gregory Price <gregory.price@memverge.com>
To: Hyeongtak Ji <hyeongtak.ji@sk.com>
Cc: gourry.memverge@gmail.com, Hasan.Maruf@amd.com,
	Jonathan.Cameron@huawei.com, akpm@linux-foundation.org,
	arnd@arndb.de, bp@alien8.de, corbet@lwn.net,
	dan.j.williams@intel.com, dave.hansen@linux.intel.com,
	emirakhur@micron.com, fvdl@google.com, hannes@cmpxchg.org,
	haowang3@fb.com, hasanalmaruf@fb.com,
	hezhongkun.hzk@bytedance.com, honggyu.kim@sk.com, hpa@zytor.com,
	jgroves@micron.com, john@jagalactic.com,
	linux-api@vger.kernel.org, linux-doc@vger.kernel.org,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, luto@kernel.org, mhocko@kernel.org,
	mhocko@suse.com, mingo@redhat.com, peterz@infradead.org,
	rakie.kim@sk.com, ravis.opensrc@micron.com,
	seungjun.ha@samsung.com, sthanneeru@micron.com,
	tglx@linutronix.de, tj@kernel.org, vtavarespetr@micron.com,
	x86@kernel.org, ying.huang@intel.com, kernel_team@skhynix.com
Subject: Re: [PATCH v3 00/11] mempolicy2, mbind2, and weighted interleave
Date: Mon, 18 Dec 2023 12:15:04 -0500	[thread overview]
Message-ID: <ZYB+GNPvzwNJUGxU@memverge.com> (raw)
In-Reply-To: <20231218070750.2123-1-hyeongtak.ji@sk.com>

On Mon, Dec 18, 2023 at 04:07:48PM +0900, Hyeongtak Ji wrote:
> Hi Gregory,
> 
> Thank you for the v3 patch.
> 
> Gregory Price <gourry.memverge@gmail.com> write:
> 
> [snip]
> 

Hi Hyeongtak!

Thanks for the tests! Added test notes to the v4 cover.

> Performance tests – XSBench
> NUMA node 0: 56 logical cores, 128 GB memory
> NUMA node 2: 96 GB CXL memory
> 
>   1. dram only
>   $ numactl -membind 0 ./XSBench -s XL –p 5000000
>   Threads:     56
>   Runtime:     36.235 seconds
>   Lookups:     170,000,000
>   Lookups/s:   4,691,618
>  
>   2. default interleave
>   $ numactl –-interleave 0,2 ./XSBench –s XL –p 5000000
>   Threads:     56
>   Runtime:     55.243 seconds
>   Lookups:     170,000,000
>   Lookups/s:   3,077,293
> 
>   3. weighted interleave
>   $ numactl --weighted --interleave 0,2 ./XSBench –s XL –p 5000000
>   Threads:     56
>   Runtime:     29.262 seconds
>   Lookups:     170,000,000
>   Lookups/s:   5,809,513
> 

  reply	other threads:[~2023-12-18 17:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-13 22:41 [PATCH v3 00/11] mempolicy2, mbind2, and weighted interleave Gregory Price
2023-12-13 22:41 ` [PATCH v3 01/11] mm/mempolicy: implement the sysfs-based weighted_interleave interface Gregory Price
2023-12-14  9:56   ` kernel test robot
2023-12-13 22:41 ` [PATCH v3 02/11] mm/mempolicy: introduce MPOL_WEIGHTED_INTERLEAVE for weighted interleaving Gregory Price
2023-12-13 22:41 ` [PATCH v3 03/11] mm/mempolicy: refactor sanitize_mpol_flags for reuse Gregory Price
2023-12-13 22:41 ` [PATCH v3 04/11] mm/mempolicy: create struct mempolicy_args for creating new mempolicies Gregory Price
2023-12-13 22:41 ` [PATCH v3 05/11] mm/mempolicy: refactor kernel_get_mempolicy for code re-use Gregory Price
2023-12-13 22:41 ` [PATCH v3 06/11] mm/mempolicy: allow home_node to be set by mpol_new Gregory Price
2023-12-13 22:41 ` [PATCH v3 07/11] mm/mempolicy: add userland mempolicy arg structure Gregory Price
2023-12-13 22:41 ` [PATCH v3 08/11] mm/mempolicy: add set_mempolicy2 syscall Gregory Price
2023-12-14 17:24   ` kernel test robot
2023-12-14 20:07   ` kernel test robot
2023-12-13 22:41 ` [PATCH v3 09/11] mm/mempolicy: add get_mempolicy2 syscall Gregory Price
2023-12-15  1:30   ` kernel test robot
2023-12-13 22:41 ` [PATCH v3 10/11] mm/mempolicy: add the mbind2 syscall Gregory Price
2023-12-13 22:41 ` [PATCH v3 11/11] mm/mempolicy: extend set_mempolicy2 and mbind2 to support weighted interleave Gregory Price
2023-12-18  7:07 ` [PATCH v3 00/11] mempolicy2, mbind2, and " Hyeongtak Ji
2023-12-18 17:15   ` Gregory Price [this message]
2023-12-18  9:42 ` Arnd Bergmann

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=ZYB+GNPvzwNJUGxU@memverge.com \
    --to=gregory.price@memverge.com \
    --cc=Hasan.Maruf@amd.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=akpm@linux-foundation.org \
    --cc=arnd@arndb.de \
    --cc=bp@alien8.de \
    --cc=corbet@lwn.net \
    --cc=dan.j.williams@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=emirakhur@micron.com \
    --cc=fvdl@google.com \
    --cc=gourry.memverge@gmail.com \
    --cc=hannes@cmpxchg.org \
    --cc=haowang3@fb.com \
    --cc=hasanalmaruf@fb.com \
    --cc=hezhongkun.hzk@bytedance.com \
    --cc=honggyu.kim@sk.com \
    --cc=hpa@zytor.com \
    --cc=hyeongtak.ji@sk.com \
    --cc=jgroves@micron.com \
    --cc=john@jagalactic.com \
    --cc=kernel_team@skhynix.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=luto@kernel.org \
    --cc=mhocko@kernel.org \
    --cc=mhocko@suse.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rakie.kim@sk.com \
    --cc=ravis.opensrc@micron.com \
    --cc=seungjun.ha@samsung.com \
    --cc=sthanneeru@micron.com \
    --cc=tglx@linutronix.de \
    --cc=tj@kernel.org \
    --cc=vtavarespetr@micron.com \
    --cc=x86@kernel.org \
    --cc=ying.huang@intel.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;
as well as URLs for NNTP newsgroup(s).