linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.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 13:31:59 +0100	[thread overview]
Message-ID: <83078db2-bc9b-4b1c-83a5-75b145173716@redhat.com> (raw)
In-Reply-To: <20240315140823.2478146-1-willy@infradead.org>

On 15.03.24 15:08, Matthew Wilcox (Oracle) wrote:
> On a 104 thread, 2 socket Skylake system, Intel report a 4.7% performance
> reduction with will-it-scale page_fault2.  This was due to reducing the
> size of the batch from 32 to 15.  Increasing the folio batch size from
> 15 to 31 gives a performance increase of 12.5% relative to the original,
> or 17.2% relative to the reduced performance commit.
> 
> The penalty of this commit is an additional 128 bytes of stack usage.
> Six folio_batches are also allocated from percpu memory in cpu_fbatches
> so that will be an additional 768 bytes of percpu memory (per CPU).
> Tim Chen originally submitted a patch like this in 2020:
> https://lore.kernel.org/linux-mm/d1cc9f12a8ad6c2a52cb600d93b06b064f2bbc57.1593205965.git.tim.c.chen@linux.intel.com/
> 
> Tested-by: Yujie Liu <yujie.liu@intel.com>
> Fixes: 99fbb6bfc16f ("mm: make folios_put() the basis of release_pages()")
> Reported-by: kernel test robot <oliver.sang@intel.com>
> Closes: https://lore.kernel.org/oe-lkp/202403151058.7048f6a8-oliver.sang@intel.com
> Signed-off-by: Matthew Wilcox (Oracle) <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;
>   

Reviewed-by: David Hildenbrand <david@redhat.com>

-- 
Cheers,

David / dhildenb



      parent reply	other threads:[~2024-03-28 12:32 UTC|newest]

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

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=83078db2-bc9b-4b1c-83a5-75b145173716@redhat.com \
    --to=david@redhat.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;
as well as URLs for NNTP newsgroup(s).