public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Luiz Capitulino <luizcap@redhat.com>
To: linux-mm@kvack.org, mgorman@techsingularity.net, willy@infradead.org
Cc: david@redhat.com, linux-kernel@vger.kernel.org, lcapitulino@gmail.com
Subject: [PATCH v2 0/2] mm: alloc_pages_bulk: small API refactor
Date: Mon, 23 Dec 2024 17:00:36 -0500	[thread overview]
Message-ID: <cover.1734991165.git.luizcap@redhat.com> (raw)

Changelog
---------

v2
- Rebased on top of v6.13-rc4
- Improve commit logs [David]
- Drop atomisp driver's free_pages_bulk_array() renaming [David]

Original intro
--------------

Hi,

Today, alloc_pages_bulk_noprof() supports two arguments to return allocated
pages: a linked list and an array. There are also higher level APIs for both.

However, the linked list API has apparently never been used. So, this series
removes it along with the list API and also refactors the remaining API naming
for consistency.

I've boot-tested this series on arm64 and built-tested it on x86.

PS: Matthew, it was easier to keep my patch instead of fixing up Mel's but I
included the API refactoring patch as well.

PPS: It's probably good to have a free_pages_bulk() function, but I'll leave
this for another day.

Luiz Capitulino (2):
  mm: alloc_pages_bulk_noprof: drop page_list argument
  mm: alloc_pages_bulk: rename API

 .../staging/media/atomisp/pci/hmm/hmm_bo.c    |  4 +-
 drivers/vfio/pci/mlx5/cmd.c                   | 14 +++----
 drivers/vfio/pci/virtio/migrate.c             |  6 +--
 fs/btrfs/extent_io.c                          |  2 +-
 fs/erofs/zutil.c                              |  4 +-
 fs/splice.c                                   |  2 +-
 fs/xfs/xfs_buf.c                              |  4 +-
 include/linux/gfp.h                           | 22 +++++------
 kernel/bpf/arena.c                            |  2 +-
 lib/alloc_tag.c                               |  4 +-
 lib/kunit_iov_iter.c                          |  2 +-
 lib/test_vmalloc.c                            |  2 +-
 mm/mempolicy.c                                | 28 ++++++-------
 mm/page_alloc.c                               | 39 ++++++-------------
 mm/vmalloc.c                                  |  4 +-
 net/core/page_pool.c                          |  7 ++--
 net/sunrpc/svc.c                              |  4 +-
 net/sunrpc/svc_xprt.c                         |  3 +-
 18 files changed, 66 insertions(+), 87 deletions(-)

-- 
2.47.1


             reply	other threads:[~2024-12-23 22:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-23 22:00 Luiz Capitulino [this message]
2024-12-23 22:00 ` [PATCH v2 1/2] mm: alloc_pages_bulk_noprof: drop page_list argument Luiz Capitulino
2024-12-25 12:36   ` Yunsheng Lin
2025-01-02 16:38     ` Luiz Capitulino
2025-01-03 11:21       ` Yunsheng Lin
2025-01-03 14:12         ` Luiz Capitulino
2025-01-02 20:00     ` Mel Gorman
2025-01-03 11:29       ` Yunsheng Lin
2025-01-03 14:27         ` Mel Gorman
2025-01-03 14:46           ` Luiz Capitulino
2025-01-08 13:39   ` David Hildenbrand
2024-12-23 22:00 ` [PATCH v2 2/2] mm: alloc_pages_bulk: rename API Luiz Capitulino
2025-01-08 13:40   ` David Hildenbrand

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=cover.1734991165.git.luizcap@redhat.com \
    --to=luizcap@redhat.com \
    --cc=david@redhat.com \
    --cc=lcapitulino@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mgorman@techsingularity.net \
    --cc=willy@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