linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Hillf Danton <hdanton@sina.com>
To: Alexey Avramov <hakavlad@inbox.lv>
Cc: Yu Zhao <yuzhao@google.com>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>,
	 "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 00/14] Multigenerational LRU Framework
Date: Sat, 7 Aug 2021 15:51:10 +0800	[thread overview]
Message-ID: <20210807075118.3BA0F6B006C@kanga.kvack.org> (raw)
In-Reply-To: <20210807150459.294f8c03@mail.inbox.lv>

[-- Attachment #1: Type: text/plain, Size: 436 bytes --]

On 7 Aug 2021 14:04 Alexey Avramov wrote:
>
>>Given no reply within two months
>
>We are discussing mgLRU outside the mailing lists.
>Some issues have been found, some have been resolved[1], some are still pending[2].

Thanks for sharing that.
What was preventing you from solving the issues at linux-mm?

>[1] https://github.com/zen-kernel/zen-kernel/issues/216
>[2] https://github.com/zen-kernel/zen-kernel/issues/223



[-- Attachment #2: Type: text/html, Size: 2562 bytes --]

      parent reply	other threads:[~2021-08-07  7:51 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-20  6:53 Yu Zhao
2021-05-20  6:53 ` [PATCH v3 01/14] include/linux/memcontrol.h: do not warn in page_memcg_rcu() if !CONFIG_MEMCG Yu Zhao
2021-05-20  6:53 ` [PATCH v3 02/14] include/linux/nodemask.h: define next_memory_node() if !CONFIG_NUMA Yu Zhao
2021-05-20  6:53 ` [PATCH v3 03/14] include/linux/cgroup.h: export cgroup_mutex Yu Zhao
2021-05-20  6:53 ` [PATCH v3 04/14] mm, x86: support the access bit on non-leaf PMD entries Yu Zhao
2021-05-20  6:53 ` [PATCH v3 05/14] mm/vmscan.c: refactor shrink_node() Yu Zhao
2021-05-20  6:53 ` [PATCH v3 06/14] mm/workingset.c: refactor pack_shadow() and unpack_shadow() Yu Zhao
2021-05-20  6:53 ` [PATCH v3 07/14] mm: multigenerational lru: groundwork Yu Zhao
2021-05-20  6:53 ` [PATCH v3 08/14] mm: multigenerational lru: activation Yu Zhao
2021-05-20  6:53 ` [PATCH v3 09/14] mm: multigenerational lru: mm_struct list Yu Zhao
2021-05-20  6:53 ` [PATCH v3 10/14] mm: multigenerational lru: aging Yu Zhao
2021-05-20  6:53 ` [PATCH v3 11/14] mm: multigenerational lru: eviction Yu Zhao
2021-05-20  6:53 ` [PATCH v3 12/14] mm: multigenerational lru: user interface Yu Zhao
2021-05-20  6:53 ` [PATCH v3 13/14] mm: multigenerational lru: Kconfig Yu Zhao
2021-05-20  6:53 ` [PATCH v3 14/14] mm: multigenerational lru: documentation Yu Zhao
2021-07-28  1:59 ` [PATCH v3 00/14] Multigenerational LRU Framework Hillf Danton
2021-08-01 17:21   ` Yu Zhao
     [not found]   ` <20210807150459.294f8c03@mail.inbox.lv>
2021-08-07  7:51     ` Hillf Danton [this message]

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=20210807075118.3BA0F6B006C@kanga.kvack.org \
    --to=hdanton@sina.com \
    --cc=hakavlad@inbox.lv \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=yuzhao@google.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox