linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Liu Ye <liuye@kylinos.cn>
To: brauner@kernel.org, dhowells@redhat.com, akpm@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Liu Ye <liuye@kylinos.cn>
Subject: [PATCH 0/2] mm: Optimize folio_order.
Date: Wed, 12 Feb 2025 10:58:41 +0800	[thread overview]
Message-ID: <20250212025843.80283-1-liuye@kylinos.cn> (raw)

Patches about folio_order.
1. Delete __folio_order and use folio_order directly.
2. Write folio->_flags_1 & 0xff as a macro definition.

Liu Ye (2):
  mm/folio_queue: Delete __folio_order and use folio_order directly
  mm/mm.h: Write folio->_flags_1 & 0xff as a macro definition

 include/linux/folio_queue.h | 12 +++---------
 include/linux/mm.h          | 10 ++++++----
 2 files changed, 9 insertions(+), 13 deletions(-)

-- 
2.25.1



             reply	other threads:[~2025-02-12  2:59 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-12  2:58 Liu Ye [this message]
2025-02-12  2:58 ` [PATCH 1/2] mm/folio_queue: Delete __folio_order and use folio_order directly Liu Ye
2025-02-12  5:19   ` Shivank Garg
2025-02-12  5:25   ` Dev Jain
2025-02-12  2:58 ` [PATCH 2/2] mm/mm.h: Write folio->_flags_1 & 0xff as a macro definition Liu Ye
2025-02-12  5:12   ` Dev Jain
2025-02-12  5:40   ` Shivank Garg
2025-02-12  7:11     ` liuye
     [not found]   ` <1739340112672653.3.seg@mailgw.kylinos.cn>
2025-02-12  7:07     ` liuye
2025-02-12  9:06       ` Dev Jain
2025-02-12 12:36   ` Matthew Wilcox
2025-02-12 16:22   ` David Hildenbrand
2025-02-12 11:28 ` [PATCH 1/2] mm/folio_queue: Delete __folio_order and use folio_order directly David Howells

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=20250212025843.80283-1-liuye@kylinos.cn \
    --to=liuye@kylinos.cn \
    --cc=akpm@linux-foundation.org \
    --cc=brauner@kernel.org \
    --cc=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox