From: Minchan Kim <minchan@kernel.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: Michal Hocko <mhocko@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
cgoldswo@codeaurora.org, linux-fsdevel@vger.kernel.org,
david@redhat.com, vbabka@suse.cz, viro@zeniv.linux.org.uk,
joaodias@google.com
Subject: Re: [RFC 1/2] mm: disable LRU pagevec during the migration temporarily
Date: Wed, 17 Feb 2021 13:22:05 -0800 [thread overview]
Message-ID: <YC2I/d2DnXRQ7eq3@google.com> (raw)
In-Reply-To: <20210217211143.GN2858050@casper.infradead.org>
On Wed, Feb 17, 2021 at 09:11:43PM +0000, Matthew Wilcox wrote:
> On Wed, Feb 17, 2021 at 12:51:25PM -0800, Minchan Kim wrote:
> > I'd like to avoid atomic operation if we could.
>
> Why do you think that the spinlock is better?
>
Michal suggested atomic_inc in writeside and atomic_read in readside.
I wanted to avoid atomic operation in readside path.
You are suggesting atomic for writeside and just read(not atomic_read)
in readside?
next prev parent reply other threads:[~2021-02-17 21:22 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-16 17:03 [RFC 1/2] mm: disable LRU pagevec during the migration temporarily Minchan Kim
2021-02-16 17:03 ` [RFC 2/2] mm: fs: Invalidate BH LRU during page migration Minchan Kim
2021-02-16 18:22 ` [RFC 1/2] mm: disable LRU pagevec during the migration temporarily Matthew Wilcox
2021-02-16 21:30 ` Minchan Kim
2021-02-17 8:59 ` Michal Hocko
2021-02-17 9:50 ` Michal Hocko
2021-02-17 20:51 ` Minchan Kim
2021-02-17 21:11 ` Matthew Wilcox
2021-02-17 21:22 ` Minchan Kim [this message]
2021-02-17 20:46 ` Minchan Kim
2021-02-17 21:16 ` Matthew Wilcox
2021-02-17 21:32 ` Minchan Kim
2021-02-18 8:17 ` Michal Hocko
2021-02-18 8:24 ` David Hildenbrand
2021-02-18 15:52 ` Minchan Kim
2021-02-18 16:08 ` Michal Hocko
2021-02-18 16:21 ` Minchan Kim
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=YC2I/d2DnXRQ7eq3@google.com \
--to=minchan@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=cgoldswo@codeaurora.org \
--cc=david@redhat.com \
--cc=joaodias@google.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).