From: Chris Li <chrisl@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: "Fabio M. De Francesco"
<fabio.maria.de.francesco@linux.intel.com>,
Seth Jennings <sjenning@redhat.com>,
Dan Streetman <ddstreet@ieee.org>,
Vitaly Wool <vitaly.wool@konsulko.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Ira Weiny <ira.weiny@intel.com>, Nhat Pham <nphamcs@gmail.com>
Subject: Re: [PATCH] mm/zswap: Replace kmap_atomic() with kmap_local_page()
Date: Tue, 28 Nov 2023 12:43:26 -0800 [thread overview]
Message-ID: <CAF8kJuPNYpHy=5fTzH5b0RoDHfCQKLkJM_APtnUQ-bs=Y60mmg@mail.gmail.com> (raw)
In-Reply-To: <ZWX0h9JEAuw4qGyV@casper.infradead.org>
Hi Matthew,
On Tue, Nov 28, 2023 at 6:09 AM Matthew Wilcox <willy@infradead.org> wrote:
> >
> > >From the performance perspective, kmap_local_page() does less so it
> > has some performance gain. I am trying to think would it have another
> > unwanted side effect of enabling interrupt and page fault while zswap
> > decompressing a page.
> > The decompression should not generate page fault. The interrupt
> > enabling might introduce extra latency, but most of the page fault was
> > having interrupt enabled anyway. The time spent in decompression is
> > relatively small compared to the whole duration of the page fault. So
> > the interrupt enabling during those short windows should be fine.
> > "Should" is the famous last word.
>
> Interrupts are enabled with kmap_atomic() too. The difference is
> whether we can be preempted by a higher-priority process.
>
You are right, thanks for the clarification.
Hi Fabio,
Acked-by: Chris Li <chrisl@kernel.org> (Google)
Chris
next prev parent reply other threads:[~2023-11-28 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-27 15:55 Fabio M. De Francesco
2023-11-27 18:07 ` Nhat Pham
2023-11-27 20:16 ` Chris Li
2023-11-28 14:09 ` Matthew Wilcox
2023-11-28 20:43 ` Chris Li [this message]
2023-11-29 11:41 ` Fabio M. De Francesco
2023-11-29 19:03 ` Christopher Li
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='CAF8kJuPNYpHy=5fTzH5b0RoDHfCQKLkJM_APtnUQ-bs=Y60mmg@mail.gmail.com' \
--to=chrisl@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=ddstreet@ieee.org \
--cc=fabio.maria.de.francesco@linux.intel.com \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nphamcs@gmail.com \
--cc=sjenning@redhat.com \
--cc=vitaly.wool@konsulko.com \
--cc=willy@infradead.org \
/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