All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Gutierrez Asier <gutierrez.asier@huawei-partners.com>
Cc: SeongJae Park <sj@kernel.org>, JaeJoon Jung <rgbi3307@gmail.com>,
	akpm@linux-foundation.org, damon@lists.linux.dev,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	wangkefeng.wang@huawei.com, artem.kuzin@huawei.com,
	stepanov.anatoly@huawei.com
Subject: Re: [RFC PATCH v1] mm: improve call_controls_lock
Date: Mon, 12 Jan 2026 07:36:40 -0800	[thread overview]
Message-ID: <20260112153641.98331-1-sj@kernel.org> (raw)
In-Reply-To: <909dbaad-f0da-4372-a151-a393619da6ec@huawei-partners.com>

On Mon, 12 Jan 2026 13:32:59 +0300 Gutierrez Asier <gutierrez.asier@huawei-partners.com> wrote:

[...] 
> I can submit a new updated patch with this small change. However,
> I believe, as discussed before, that the improvement in general will 
> be small and it may not be worth it.

I agree.  I don't think we need the updated patch for now.


Thanks,
SJ

[...]

  reply	other threads:[~2026-01-12 15:36 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-29 14:55 [RFC PATCH v1] mm: improve call_controls_lock Asier Gutierrez
2025-12-29 15:22 ` SeongJae Park
2025-12-30  9:02   ` Gutierrez Asier
2025-12-31  5:01     ` SeongJae Park
2025-12-31  2:15   ` JaeJoon Jung
2025-12-31  4:59     ` SeongJae Park
2025-12-31  6:10       ` JaeJoon Jung
2025-12-31  7:51         ` JaeJoon Jung
2026-01-12 10:32           ` Gutierrez Asier
2026-01-12 15:36             ` SeongJae Park [this message]
2025-12-31 15:32         ` SeongJae Park
2026-01-01  1:11           ` JaeJoon Jung
2026-01-01  2:00             ` SeongJae Park
2026-01-01  2:34               ` JaeJoon Jung
2026-01-01 22:44                 ` SeongJae Park
2026-01-01  1:07       ` JaeJoon Jung
2026-01-01  1:51         ` SeongJae Park
2026-01-01  2:29           ` JaeJoon Jung
2026-01-06  6:41 ` kernel test robot

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=20260112153641.98331-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=artem.kuzin@huawei.com \
    --cc=damon@lists.linux.dev \
    --cc=gutierrez.asier@huawei-partners.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=rgbi3307@gmail.com \
    --cc=stepanov.anatoly@huawei.com \
    --cc=wangkefeng.wang@huawei.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.