linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Mike Kravetz <mike.kravetz@oracle.com>
Cc: Muchun Song <muchun.song@linux.dev>,
	linux-mm@kvack.org, Sidhartha Kumar <sidhartha.kumar@oracle.com>
Subject: Re: [PATCH 3/3] hugetlb: Convert remove_pool_huge_page() to return a folio
Date: Thu, 24 Aug 2023 02:10:31 +0100	[thread overview]
Message-ID: <ZOauB71roGjmx00w@casper.infradead.org> (raw)
In-Reply-To: <20230823224813.GH50463@monkey>

On Wed, Aug 23, 2023 at 03:48:13PM -0700, Mike Kravetz wrote:
> > -static struct page *remove_pool_huge_page(struct hstate *h,
> > -						nodemask_t *nodes_allowed,
> > -						 bool acct_surplus)
> > +static struct folio *remove_pool_huge_page(struct hstate *h,
> > +		nodemask_t *nodes_allowed, bool acct_surplus)
> 
> might have been good to make a simple name change to remove_pool_huge_folio,
> but not insisting.

I wasn't sure what we were calling it now.  I can go for huge_folio.


  reply	other threads:[~2023-08-24  1:10 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-22 16:28 [PATCH 1/3] hugetlb: Use a folio in free_hpage_workfn() Matthew Wilcox (Oracle)
2023-08-22 16:28 ` [PATCH 2/3] hugetlb: Remove a few calls to page_folio() Matthew Wilcox (Oracle)
2023-08-23 22:41   ` Mike Kravetz
2023-08-24  2:59   ` Muchun Song
2023-08-24 13:59   ` kernel test robot
2023-10-13  9:06   ` Dan Carpenter
2023-08-22 16:28 ` [PATCH 3/3] hugetlb: Convert remove_pool_huge_page() to return a folio Matthew Wilcox (Oracle)
2023-08-23 22:48   ` Mike Kravetz
2023-08-24  1:10     ` Matthew Wilcox [this message]
2023-08-24  2:38       ` Muchun Song
2023-08-23 22:37 ` [PATCH 1/3] hugetlb: Use a folio in free_hpage_workfn() Mike Kravetz
2023-08-24  2:58 ` Muchun Song

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=ZOauB71roGjmx00w@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=linux-mm@kvack.org \
    --cc=mike.kravetz@oracle.com \
    --cc=muchun.song@linux.dev \
    --cc=sidhartha.kumar@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox