From: Alex Shi <alex.shi@linux.alibaba.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Wei Yang <richard.weiyang@gmail.com>,
Hugh Dickins <hughd@google.com>,
"Kirill A. Shutemov" <kirill@shutemov.name>,
Andrea Arcangeli <aarcange@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Thomas Gleixner <tglx@linutronix.de>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH 4/4] mm/thp: narrow lru locking
Date: Sun, 2 Aug 2020 21:24:32 +0800 [thread overview]
Message-ID: <2504ea84-110c-cf8e-d2f7-0aab97f6121a@linux.alibaba.com> (raw)
In-Reply-To: <20200802110925.GW23808@casper.infradead.org>
在 2020/8/2 下午7:09, Matthew Wilcox 写道:
> You're playing games with separating interrupt disabling from spinlocks.
> Have you got any feedback from -rt people on this?
Is there other suggestions to remove local_irq_disable?
Just check again on kernel/mm directory on linux-next. there are still
much local_irq_disable there.
Guess we need a final solution instead of block new one.
Thanks
Alex
next prev parent reply other threads:[~2020-08-02 13:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-01 4:09 [PATCH 1/4] mm/thp: move lru_add_page_tail func to huge_memory.c Alex Shi
2020-08-01 4:09 ` [PATCH 2/4] mm/thp: clean up lru_add_page_tail Alex Shi
2020-08-01 4:09 ` [PATCH 3/4] mm/thp: remove code path which never got into Alex Shi
2020-08-01 4:09 ` [PATCH 4/4] mm/thp: narrow lru locking Alex Shi
2020-08-02 11:09 ` Matthew Wilcox
2020-08-02 13:24 ` Alex Shi [this message]
2020-08-01 4:11 ` [PATCH 1/4] mm/thp: move lru_add_page_tail func to huge_memory.c Alex Shi
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=2504ea84-110c-cf8e-d2f7-0aab97f6121a@linux.alibaba.com \
--to=alex.shi@linux.alibaba.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=hannes@cmpxchg.org \
--cc=hughd@google.com \
--cc=kirill@shutemov.name \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=peterz@infradead.org \
--cc=richard.weiyang@gmail.com \
--cc=tglx@linutronix.de \
--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).