linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: "Garg, Shivank" <shivankg@amd.com>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>,
	Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, Yujie Liu <yujie.liu@intel.com>,
	kernel test robot <oliver.sang@intel.com>
Subject: Re: [PATCH] mm: Increase folio batch size
Date: Thu, 28 Mar 2024 16:26:33 +0530	[thread overview]
Message-ID: <8140c23f-4dd1-4c44-b236-7ea3745b5d8d@amd.com> (raw)
In-Reply-To: <20240315140823.2478146-1-willy@infradead.org>

>  include/linux/pagevec.h | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/include/linux/pagevec.h b/include/linux/pagevec.h
> index fcc06c300a72..5d3a0cccc6bf 100644
> --- a/include/linux/pagevec.h
> +++ b/include/linux/pagevec.h
> @@ -11,8 +11,8 @@
>  
>  #include <linux/types.h>
>  
> -/* 15 pointers + header align the folio_batch structure to a power of two */
> -#define PAGEVEC_SIZE	15
> +/* 31 pointers + header align the folio_batch structure to a power of two */
> +#define PAGEVEC_SIZE	31
>  
>  struct folio;
>  

Hi,

Thanks for the patch.
I tested the patch with will-it-scale page-fault2 on AMD Zen 4 EPYC server (2-socket system with 128 cores per socket, SMT Enabled). 

Increasing the folio batch size from 15 to 31 gives following performance improvement:
Median: 8.32% 
Max: 23.15%
99th percentile: 20.95%

There is slight performance degradation (bound by -1.21%) in a few cases.

The patch seems to be beneficial for AMD systems as well.

Tested-by: Shivank Garg <shivankg@amd.com>

--
Best Regards,
Shivank




  reply	other threads:[~2024-03-28 10:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-15 14:08 Matthew Wilcox (Oracle)
2024-03-28 10:56 ` Garg, Shivank [this message]
2024-03-28 12:31 ` David Hildenbrand

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=8140c23f-4dd1-4c44-b236-7ea3745b5d8d@amd.com \
    --to=shivankg@amd.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=oliver.sang@intel.com \
    --cc=willy@infradead.org \
    --cc=yujie.liu@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