All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Kirill Tkhai <ktkhai@virtuozzo.com>
Cc: vdavydov.dev@gmail.com, shakeelb@google.com,
	viro@zeniv.linux.org.uk, hannes@cmpxchg.org, mhocko@kernel.org,
	tglx@linutronix.de, pombredanne@nexb.com,
	stummala@codeaurora.org, gregkh@linuxfoundation.org,
	sfr@canb.auug.org.au, guro@fb.com, mka@chromium.org,
	penguin-kernel@I-love.SAKURA.ne.jp, chris@chris-wilson.co.uk,
	longman@redhat.com, minchan@kernel.org, ying.huang@intel.com,
	mgorman@techsingularity.net, jbacik@fb.com, linux@roeck-us.net,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	willy@infradead.org, lirongqing@baidu.com,
	aryabinin@virtuozzo.com,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH v7 REBASED 00/17] Improve shrink_slab() scalability (old complexity was O(n^2), new is O(n))
Date: Mon, 2 Jul 2018 14:01:09 -0700	[thread overview]
Message-ID: <20180702140109.38f65bdc5cb48b47f923b610@linux-foundation.org> (raw)
In-Reply-To: <46d951be-d3c4-91a0-0e33-711591914470@virtuozzo.com>

On Mon, 2 Jul 2018 12:10:47 +0300 Kirill Tkhai <ktkhai@virtuozzo.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.

  reply	other threads:[~2018-07-02 21:01 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-18  9:44 [PATCH v7 REBASED 00/17] Improve shrink_slab() scalability (old complexity was O(n^2), new is O(n)) Kirill Tkhai
2018-06-18  9:44 ` [PATCH v7 REBASED 01/17] list_lru: Combine code under the same define Kirill Tkhai
2018-06-18  9:45 ` [PATCH v7 REBASED 02/17] mm: Introduce CONFIG_MEMCG_KMEM as combination of CONFIG_MEMCG && !CONFIG_SLOB Kirill Tkhai
2018-06-18  9:45 ` [PATCH v7 REBASED 03/17] mm: Assign id to every memcg-aware shrinker Kirill Tkhai
2018-06-18  9:45 ` [PATCH v7 REBASED 04/17] memcg: Move up for_each_mem_cgroup{, _tree} defines Kirill Tkhai
2018-06-18  9:45 ` [PATCH v7 REBASED 05/17] mm: Assign memcg-aware shrinkers bitmap to memcg Kirill Tkhai
2018-06-18  9:45 ` [PATCH v7 REBASED 06/17] mm: Refactoring in workingset_init() Kirill Tkhai
2018-06-18  9:45 ` [PATCH v7 REBASED 07/17] fs: Refactoring in alloc_super() Kirill Tkhai
2018-06-18  9:46 ` [PATCH v7 REBASED 08/17] fs: Propagate shrinker::id to list_lru Kirill Tkhai
2018-06-18  9:46 ` [PATCH v7 REBASED 09/17] list_lru: Add memcg argument to list_lru_from_kmem() Kirill Tkhai
2018-06-18  9:46 ` [PATCH v7 REBASED 10/17] list_lru: Pass dst_memcg argument to memcg_drain_list_lru_node() Kirill Tkhai
2018-06-18  9:46 ` [PATCH v7 REBASED 11/17] list_lru: Pass lru " Kirill Tkhai
2018-06-18  9:46 ` [PATCH v7 REBASED 12/17] mm: Export mem_cgroup_is_root() Kirill Tkhai
2018-06-18  9:47 ` [PATCH v7 REBASED 13/17] mm: Set bit in memcg shrinker bitmap on first list_lru item apearance Kirill Tkhai
2018-06-18  9:47 ` [PATCH v7 REBASED 14/17] mm: Iterate only over charged shrinkers during memcg shrink_slab() Kirill Tkhai
2018-06-18  9:47 ` [PATCH v7 REBASED 15/17] mm: Generalize shrink_slab() calls in shrink_node() Kirill Tkhai
2018-06-18  9:47 ` [PATCH v7 REBASED 16/17] mm: Add SHRINK_EMPTY shrinker methods return value Kirill Tkhai
2018-06-18  9:47 ` [PATCH v7 REBASED 17/17] mm: Clear shrinker bit if there are no objects related to memcg Kirill Tkhai
2018-07-02  9:10 ` [PATCH v7 REBASED 00/17] Improve shrink_slab() scalability (old complexity was O(n^2), new is O(n)) Kirill Tkhai
2018-07-02 21:01   ` Andrew Morton [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-18  9:39 Kirill Tkhai

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=20180702140109.38f65bdc5cb48b47f923b610@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=aryabinin@virtuozzo.com \
    --cc=bigeasy@linutronix.de \
    --cc=chris@chris-wilson.co.uk \
    --cc=gregkh@linuxfoundation.org \
    --cc=guro@fb.com \
    --cc=hannes@cmpxchg.org \
    --cc=jbacik@fb.com \
    --cc=ktkhai@virtuozzo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=linux@roeck-us.net \
    --cc=lirongqing@baidu.com \
    --cc=longman@redhat.com \
    --cc=mgorman@techsingularity.net \
    --cc=mhocko@kernel.org \
    --cc=minchan@kernel.org \
    --cc=mka@chromium.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=pombredanne@nexb.com \
    --cc=sfr@canb.auug.org.au \
    --cc=shakeelb@google.com \
    --cc=stummala@codeaurora.org \
    --cc=tglx@linutronix.de \
    --cc=vdavydov.dev@gmail.com \
    --cc=viro@zeniv.linux.org.uk \
    --cc=willy@infradead.org \
    --cc=ying.huang@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.