From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,hannes@cmpxchg.org,cerasuolodomenico@gmail.com,hezhongkun.hzk@bytedance.com,akpm@linux-foundation.org
Subject: [to-be-updated] mm-z3fold-remove-unneeded-spinlock-in-z3fold_alloc.patch removed from -mm tree
Date: Wed, 21 Feb 2024 14:24:15 -0800 [thread overview]
Message-ID: <20240221222416.3B2F5C43390@smtp.kernel.org> (raw)
The quilt patch titled
Subject: mm/z3fold: remove unneeded spinlock in z3fold_alloc
has been removed from the -mm tree. Its filename was
mm-z3fold-remove-unneeded-spinlock-in-z3fold_alloc.patch
This patch was dropped because an updated version will be merged
------------------------------------------------------
From: Zhongkun He <hezhongkun.hzk@bytedance.com>
Subject: mm/z3fold: remove unneeded spinlock in z3fold_alloc
Date: Sun, 4 Feb 2024 21:15:43 +0800
The spinlock in z3fold_alloc() is used to protect page->lru, but now it
was removed in commit e774a7bc7f0ad ("mm: zswap: remove page reclaim logic
from z3fold"), so remove the spinlock too.
Link: https://lkml.kernel.org/r/20240204131543.1469661-1-hezhongkun.hzk@bytedance.com
Signed-off-by: Zhongkun He <hezhongkun.hzk@bytedance.com>
Cc: Domenico Cerasuolo <cerasuolodomenico@gmail.com>
Cc: Johannes Weiner <hannes@cmpxchg.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
mm/z3fold.c | 2 --
1 file changed, 2 deletions(-)
--- a/mm/z3fold.c~mm-z3fold-remove-unneeded-spinlock-in-z3fold_alloc
+++ a/mm/z3fold.c
@@ -1070,9 +1070,7 @@ found:
add_to_unbuddied(pool, zhdr);
headless:
- spin_lock(&pool->lock);
*handle = encode_handle(zhdr, bud);
- spin_unlock(&pool->lock);
if (bud != HEADLESS)
z3fold_page_unlock(zhdr);
_
Patches currently in -mm which might be from hezhongkun.hzk@bytedance.com are
mm-z3fold-fix-the-comment-for-__encode_handle.patch
reply other threads:[~2024-02-21 22:24 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240221222416.3B2F5C43390@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=cerasuolodomenico@gmail.com \
--cc=hannes@cmpxchg.org \
--cc=hezhongkun.hzk@bytedance.com \
--cc=mm-commits@vger.kernel.org \
/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.