[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20180702140109.38f65bdc5cb48b47f923b610@linux-foundation.org>
Date: Mon, 2 Jul 2018 14:01:09 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Kirill Tkhai <ktkhai@...tuozzo.com>
Cc: vdavydov.dev@...il.com, shakeelb@...gle.com,
viro@...iv.linux.org.uk, hannes@...xchg.org, mhocko@...nel.org,
tglx@...utronix.de, pombredanne@...b.com, stummala@...eaurora.org,
gregkh@...uxfoundation.org, sfr@...b.auug.org.au, guro@...com,
mka@...omium.org, penguin-kernel@...ove.SAKURA.ne.jp,
chris@...is-wilson.co.uk, longman@...hat.com, minchan@...nel.org,
ying.huang@...el.com, mgorman@...hsingularity.net, jbacik@...com,
linux@...ck-us.net, linux-kernel@...r.kernel.org,
linux-mm@...ck.org, willy@...radead.org, lirongqing@...du.com,
aryabinin@...tuozzo.com,
Sebastian Andrzej Siewior <bigeasy@...utronix.de>
Subject: Re: [PATCH v7 REBASED 00/17] Improve shrink_slab() scalability (old
complexity was O(n^2), new is O(n))
On Mon, 2 Jul 2018 12:10:47 +0300 Kirill Tkhai <ktkhai@...tuozzo.com> wrote:
> Hi, Andrew,
>
> this series is made on top of 4.18-rc1, while now I see "mm-list_lru-add-lock_irq-member-to-__list_lru_init.patch"
> in mm tree, which conflicts with two of patches from series.
Well, "mm: use irq locking suffix instead local_irq_disable()" is a
fairly straightforward cleanup series, so it would be best to base your
patches on that work, please.
There is a significant review comment from Vladimir against "mm:
list_lru: add lock_irq member to __list_lru_init()" to which Sebastian
has yet to respond (please).
> Should I rebase the series on top of current mm tree? What are you plans on this series?
It looks like they're ready for an initial merge.
Powered by blists - more mailing lists