From: Barry Song <21cnbao@gmail.com>
To: Kanchana P Sridhar <kanchana.p.sridhar@intel.com>
Cc: akpm@linux-foundation.org, baolin.wang@linux.alibaba.com,
chrisl@kernel.org, david@redhat.com, hanchuanhua@oppo.com,
hannes@cmpxchg.org, hch@infradead.org, hughd@google.com,
kaleshsingh@google.com, kasong@tencent.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
mhocko@suse.com, minchan@kernel.org, nphamcs@gmail.com,
ryan.roberts@arm.com, ryncsn@gmail.com,
senozhatsky@chromium.org, shakeel.butt@linux.dev,
shy828301@gmail.com, surenb@google.com, v-songbaohua@oppo.com,
willy@infradead.org, xiang@kernel.org, ying.huang@intel.com,
yosryahmed@google.com, zhengtangquan@oppo.com,
wajdi.k.feghali@intel.com, vinodh.gopal@intel.com
Subject: Re: [PATCH v7 2/2] mm: support large folios swap-in for sync io devices
Date: Thu, 29 Aug 2024 14:24:56 +1200 [thread overview]
Message-ID: <CAGsJ_4xLCknyaWk1a5RZ9h77QkamBxKi6HbjVhCbXPS9rm0WZg@mail.gmail.com> (raw)
In-Reply-To: <20240829010103.7705-1-kanchana.p.sridhar@intel.com>
On Thu, Aug 29, 2024 at 1:01 PM Kanchana P Sridhar
<kanchana.p.sridhar@intel.com> wrote:
>
> Hi Shakeel,
>
> We submitted an RFC patchset [1] with the Intel In-Memory Analytics
> Accelerator (Intel IAA) sometime back. This introduces a new 'canned-by_n'
> compression algorithm in the IAA crypto driver.
>
> Relative to software compressors, we could get a 10X improvement in zram
> write latency and 7X improvement in zram read latency.
>
> [1] https://lore.kernel.org/all/cover.1714581792.git.andre.glover@linux.intel.com/
Hi Kanchana,
Thanks for sharing. I understand you’ll need this mTHP swap-in series
to leverage your
IAA for parallel decompression, right? Without mTHP swap-in, you won't
get this 7X
improvement, right?
This is another important use case for the mTHP swap-in series,
highlighting the strong
need to start the work from the sync IO device.
I’ll try to find some time to review your patch and explore how we can
better support both
software and hardware improvements in zsmalloc/zram with a more
compatible approach.
Also, I have a talk[1] at LPC2024—would you mind if I include a
description of your use
case?
[1] https://lpc.events/event/18/contributions/1780/
>
> Thanks,
> Kanchana
Thanks
Barry
next prev parent reply other threads:[~2024-08-29 2:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 7:45 [PATCH v7 0/2] mm: Ignite large folios swap-in support hanchuanhua
2024-08-21 7:45 ` [PATCH v7 1/2] mm: add nr argument in mem_cgroup_swapin_uncharge_swap() helper to support large folios hanchuanhua
2024-08-21 7:45 ` [PATCH v7 2/2] mm: support large folios swap-in for sync io devices hanchuanhua
2024-08-21 17:31 ` Shakeel Butt
2024-08-21 21:13 ` Barry Song
2024-08-23 17:56 ` Shakeel Butt
2024-08-26 19:46 ` Barry Song
2024-08-29 1:01 ` Kanchana P Sridhar
2024-08-29 2:24 ` Barry Song [this message]
2024-08-29 2:38 ` Sridhar, Kanchana P
2024-09-03 18:24 ` Kairui Song
2024-09-03 18:38 ` Yosry Ahmed
2024-09-03 20:07 ` Andrew Morton
2024-09-03 21:36 ` Barry Song
2024-09-03 22:05 ` Yosry Ahmed
2024-09-04 21:30 ` Usama Arif
2024-09-04 23:10 ` Barry Song
2024-09-04 23:23 ` Usama Arif
2024-09-04 23:27 ` Barry Song
2024-09-04 23:35 ` Yosry Ahmed
2024-09-22 23:57 ` Barry Song
2024-09-23 10:22 ` Usama Arif
2024-09-23 12:10 ` Johannes Weiner
2024-09-23 16:53 ` Yosry Ahmed
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=CAGsJ_4xLCknyaWk1a5RZ9h77QkamBxKi6HbjVhCbXPS9rm0WZg@mail.gmail.com \
--to=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=chrisl@kernel.org \
--cc=david@redhat.com \
--cc=hanchuanhua@oppo.com \
--cc=hannes@cmpxchg.org \
--cc=hch@infradead.org \
--cc=hughd@google.com \
--cc=kaleshsingh@google.com \
--cc=kanchana.p.sridhar@intel.com \
--cc=kasong@tencent.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=minchan@kernel.org \
--cc=nphamcs@gmail.com \
--cc=ryan.roberts@arm.com \
--cc=ryncsn@gmail.com \
--cc=senozhatsky@chromium.org \
--cc=shakeel.butt@linux.dev \
--cc=shy828301@gmail.com \
--cc=surenb@google.com \
--cc=v-songbaohua@oppo.com \
--cc=vinodh.gopal@intel.com \
--cc=wajdi.k.feghali@intel.com \
--cc=willy@infradead.org \
--cc=xiang@kernel.org \
--cc=ying.huang@intel.com \
--cc=yosryahmed@google.com \
--cc=zhengtangquan@oppo.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