All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baolin Wang <baolin.wang@linux.alibaba.com>
To: Andrew Morton <akpm@linux-foundation.org>,
	Lorenzo Stoakes <ljs@kernel.org>
Cc: hughd@google.com, willy@infradead.org, ziy@nvidia.com,
	david@kernel.org, lance.yang@linux.dev,
	wangkefeng.wang@huawei.com, linux-mm@kvack.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Revert "tmpfs: don't enable large folios if not supported"
Date: Tue, 12 May 2026 08:55:05 +0800	[thread overview]
Message-ID: <b1302558-e5a0-4963-b9ed-533d35dea802@linux.alibaba.com> (raw)
In-Reply-To: <20260511150158.921c0ac72b31a6fa0a125ab8@linux-foundation.org>



On 5/12/26 6:01 AM, Andrew Morton wrote:
> On Mon, 11 May 2026 13:03:04 +0100 Lorenzo Stoakes <ljs@kernel.org> wrote:
> 
>> On Wed, May 06, 2026 at 04:58:20PM +0800, Baolin Wang wrote:
>>>
>>>
>>> On 5/5/26 6:47 PM, Lorenzo Stoakes wrote:
>>>> On Tue, May 05, 2026 at 11:46:11AM +0100, Lorenzo Stoakes wrote:
>>>>> Acked-by: Lorenzo Stoakes <ljs@kernel.org>
>>>>>
>>>>> As David asked, should we have a Fixes tag? What about cc: stable?
>>>
>>> Sure. But this fix tag depends on the commit 665575cff098b, so the fixes tag
>>> should be:
>>>
>>> Fixes: 5a90c155defa ("tmpfs: don't enable large folios if not supported")
>>> Depends-on: 665575cff098b ("filemap: move prefaulting out of hot write
>>> path").
>>
>> Oh is Depends-on a tag? Wasn't aware of it :>)
> 
> It is not.
> 
> hp2:/usr/src/25> grep -ri Depends-on Documentation | wc -l
> 0
> 
> But it is!
> 
> hp2:/usr/src/25> grep -ri Depends-on ../gitlog | wc -l
> 156
> 
> I actually removed it because a) various tools whine at me and b) we
> didn't cc:stable anyway.

Okay, I remember I've seen that tag :)

> 
> Please let's not add new metadata without having told others what that
> metadata means?
> 
> "Fixes:" should be sufficient.  I interpret Fixes: as "apply this to any
> kernel which contains <that>".  Is more needed?

My concern is that if someone backports this patch to an older kernel 
version without also backporting commit 665575cff098b, it would cause a 
performance regression.

Is there a good way to mark this kind of dependency on another patch? 
But I've already described this potential dependency in the commit 
message, so I'm fine with just adding the "Fixes:" tag.


  reply	other threads:[~2026-05-12  0:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-23  1:41 [PATCH] Revert "tmpfs: don't enable large folios if not supported" Baolin Wang
2026-04-23  2:37 ` Zi Yan
2026-04-23  2:46 ` Kefeng Wang
2026-04-23  2:57 ` Lance Yang
2026-04-23 13:20 ` David Hildenbrand (Arm)
2026-04-26  5:55   ` Baolin Wang
2026-05-05 10:46 ` Lorenzo Stoakes
2026-05-05 10:47   ` Lorenzo Stoakes
2026-05-06  8:58     ` Baolin Wang
2026-05-11 12:03       ` Lorenzo Stoakes
2026-05-11 22:01         ` Andrew Morton
2026-05-12  0:55           ` Baolin Wang [this message]
2026-05-12  1:15             ` Andrew Morton

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=b1302558-e5a0-4963-b9ed-533d35dea802@linux.alibaba.com \
    --to=baolin.wang@linux.alibaba.com \
    --cc=akpm@linux-foundation.org \
    --cc=david@kernel.org \
    --cc=hughd@google.com \
    --cc=lance.yang@linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=wangkefeng.wang@huawei.com \
    --cc=willy@infradead.org \
    --cc=ziy@nvidia.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.