linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: Liam.Howlett@oracle.com, akpm@linux-foundation.org
Cc: maple-tree@lists.infradead.org, linux-mm@kvack.org,
	Wei Yang <richard.weiyang@gmail.com>
Subject: [PATCH 0/4] cleanup maple_alloc related functions
Date: Tue, 24 Sep 2024 12:39:50 +0000	[thread overview]
Message-ID: <20240924123954.18933-1-richard.weiyang@gmail.com> (raw)

Patch 1/2: some fields of the maple_alloc is not necessary to change, so we
           can skip some operations
Patch 3: a valid alloc check could be hide in current code, so we don't need
         to do a separate check
Patch 4: found on rare case where allocation would fail even has enough
         memory

Wei Yang (4):
  maple_tree: clear request_count for new allocated one
  maple_tree: total is not changed for nomem_one case
  maple_tree: simplify mas_push_node()
  maple_tree: fix potential allocation failure even has memory

 lib/maple_tree.c | 26 ++++++++++++--------------
 1 file changed, 12 insertions(+), 14 deletions(-)

-- 
2.34.1



             reply	other threads:[~2024-09-24 12:41 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-24 12:39 Wei Yang [this message]
2024-09-24 12:39 ` [PATCH 1/4] maple_tree: clear request_count for new allocated one Wei Yang
2024-10-15  1:18   ` Liam R. Howlett
2024-09-24 12:39 ` [PATCH 2/4] maple_tree: total is not changed for nomem_one case Wei Yang
2024-10-15  1:20   ` Liam R. Howlett
2024-09-24 12:39 ` [PATCH 3/4] maple_tree: simplify mas_push_node() Wei Yang
2024-10-15  1:29   ` Liam R. Howlett
2024-09-24 12:39 ` [PATCH 4/4] maple_tree: fix potential allocation failure even has memory Wei Yang
2024-10-11  1:27   ` Wei Yang
2024-10-15  1:14     ` Liam R. Howlett
2024-10-15  1:29     ` Liam R. Howlett
2024-09-24 15:03 ` [PATCH 0/4] cleanup maple_alloc related functions Lorenzo Stoakes
2024-09-25  1:03   ` Wei Yang
2024-09-25  7:41     ` Lorenzo Stoakes

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=20240924123954.18933-1-richard.weiyang@gmail.com \
    --to=richard.weiyang@gmail.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-mm@kvack.org \
    --cc=maple-tree@lists.infradead.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