From: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
To: Usama Arif <usamaarif642@gmail.com>, akpm@linux-foundation.org
Cc: hannes@cmpxchg.org, shakeel.butt@linux.dev, david@redhat.com,
ying.huang@intel.com, hughd@google.com, willy@infradead.org,
yosryahmed@google.com, nphamcs@gmail.com,
chengming.zhou@linux.dev, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kernel-team@meta.com,
Andi Kleen <ak@linux.intel.com>
Subject: Re: [RESEND v8 1/2] mm: store zero pages to be swapped out in a bitmap
Date: Sat, 24 Aug 2024 08:55:25 +0200 [thread overview]
Message-ID: <70a3d71d-b0f9-48b8-bb00-497cd17da764@wanadoo.fr> (raw)
In-Reply-To: <20240823190545.979059-2-usamaarif642@gmail.com>
Le 23/08/2024 à 21:04, Usama Arif a écrit :
> Approximately 10-20% of pages to be swapped out are zero pages [1].
> Rather than reading/writing these pages to flash resulting
> in increased I/O and flash wear, a bitmap can be used to mark these
> pages as zero at write time, and the pages can be filled at
> read time if the bit corresponding to the page is set.
> With this patch, NVMe writes in Meta server fleet decreased
> by almost 10% with conventional swap setup (zswap disabled).
>
> [1] https://lore.kernel.org/all/20171018104832epcms5p1b2232e2236258de3d03d1344dde9fce0@epcms5p1/
>
...
> @@ -3428,6 +3444,17 @@ SYSCALL_DEFINE2(swapon, const char __user *, specialfile, int, swap_flags)
> goto bad_swap_unlock_inode;
> }
>
> + /*
> + * Use kvmalloc_array instead of bitmap_zalloc as the allocation order might
> + * be above MAX_PAGE_ORDER incase of a large swap file.
> + */
> + zeromap = kvmalloc_array(BITS_TO_LONGS(maxpages), sizeof(long),
> + GFP_KERNEL | __GFP_ZERO);
Nitpick: kvcalloc() maybe, to be slightly less verbose?
> + if (!zeromap) {
> + error = -ENOMEM;
> + goto bad_swap_unlock_inode;
> + }
> +
> if (si->bdev && bdev_stable_writes(si->bdev))
> si->flags |= SWP_STABLE_WRITES;
>
...
CJ
next prev parent reply other threads:[~2024-08-24 6:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-23 19:04 [RESEND v8 0/2] " Usama Arif
2024-08-23 19:04 ` [RESEND v8 1/2] " Usama Arif
2024-08-24 6:55 ` Christophe JAILLET [this message]
2024-08-24 18:58 ` Usama Arif
2024-08-23 19:04 ` [RESEND v8 2/2] mm: remove code to handle same filled pages Usama Arif
2024-08-24 5:06 ` [RESEND v8 0/2] mm: store zero pages to be swapped out in a bitmap Andrew Morton
2024-08-24 18:47 ` Usama Arif
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=70a3d71d-b0f9-48b8-bb00-497cd17da764@wanadoo.fr \
--to=christophe.jaillet@wanadoo.fr \
--cc=ak@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=david@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=shakeel.butt@linux.dev \
--cc=usamaarif642@gmail.com \
--cc=willy@infradead.org \
--cc=ying.huang@intel.com \
--cc=yosryahmed@google.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
all inboxes | Powered by JetHome®