All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Kravetz <mike.kravetz@oracle.com>
To: Muchun Song <muchun.song@linux.dev>
Cc: Linux-MM <linux-mm@kvack.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Muchun Song <songmuchun@bytedance.com>,
	Joao Martins <joao.m.martins@oracle.com>,
	Oscar Salvador <osalvador@suse.de>,
	David Hildenbrand <david@redhat.com>,
	Miaohe Lin <linmiaohe@huawei.com>,
	David Rientjes <rientjes@google.com>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Naoya Horiguchi <naoya.horiguchi@linux.dev>,
	Barry Song <21cnbao@gmail.com>, Michal Hocko <mhocko@suse.com>,
	Matthew Wilcox <willy@infradead.org>,
	Xiongchun Duan <duanxiongchun@bytedance.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v4 4/8] hugetlb: perform vmemmap restoration on a list of pages
Date: Fri, 22 Sep 2023 10:28:24 -0700	[thread overview]
Message-ID: <20230922172824.GC224968@monkey> (raw)
In-Reply-To: <20230922170101.GB224968@monkey>

On 09/22/23 10:01, Mike Kravetz wrote:
> On 09/22/23 16:19, Muchun Song wrote:
> > On 2023/9/22 05:58, Mike Kravetz wrote:
> > > On 09/21/23 17:31, Muchun Song wrote:
> > > > On 2023/9/21 09:12, Mike Kravetz wrote:
> > > > > On 09/20/23 11:03, Muchun Song wrote:
> > > + */
> > > +int hugetlb_vmemmap_restore_folios(const struct hstate *h,
> > > +					struct list_head *folio_list,
> > > +					struct list_head *non_op_list)
> > 
> > non_optimized_list or vmemmap_intact_list? The abbreviation is not
> > straightforward.
> > 
> 
> Ok, I will be more specific.  non_optimized_list is better.
> 

I changed my mind.
The longer name caused 80 column line wrap that I didn't like. :)

I will use non_hvo_folios.  The abbreviation hvo is pretty specific
in this context.
-- 
Mike Kravetz


  reply	other threads:[~2023-09-22 17:29 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-18 23:01 [PATCH v4 0/8] Batch hugetlb vmemmap modification operations Mike Kravetz
2023-09-18 23:01 ` [PATCH v4 1/8] hugetlb: optimize update_and_free_pages_bulk to avoid lock cycles Mike Kravetz
2023-09-18 23:01 ` [PATCH v4 2/8] hugetlb: restructure pool allocations Mike Kravetz
2023-09-18 23:01 ` [PATCH v4 3/8] hugetlb: perform vmemmap optimization on a list of pages Mike Kravetz
2023-09-19  3:10   ` Muchun Song
2023-09-19 20:49     ` Mike Kravetz
2023-09-20  3:05       ` Muchun Song
2023-09-18 23:01 ` [PATCH v4 4/8] hugetlb: perform vmemmap restoration " Mike Kravetz
2023-09-19  9:52   ` Muchun Song
2023-09-19 20:57     ` Mike Kravetz
2023-09-20  2:56       ` Muchun Song
2023-09-20  3:03         ` Muchun Song
2023-09-21  1:12           ` Mike Kravetz
2023-09-21  9:31             ` Muchun Song
2023-09-21  9:47               ` Muchun Song
2023-09-21 21:58               ` Mike Kravetz
2023-09-22  8:19                 ` Muchun Song
2023-09-22 17:01                   ` Mike Kravetz
2023-09-22 17:28                     ` Mike Kravetz [this message]
2023-09-18 23:01 ` [PATCH v4 5/8] hugetlb: batch freeing of vmemmap pages Mike Kravetz
2023-09-19  6:09   ` Muchun Song
2023-09-19 21:32     ` Mike Kravetz
2023-09-18 23:01 ` [PATCH v4 6/8] hugetlb: batch PMD split for bulk vmemmap dedup Mike Kravetz
2023-09-19  6:27   ` Muchun Song
2023-09-19  8:18     ` Joao Martins
2023-09-19  6:42   ` Muchun Song
2023-09-19  8:26     ` Joao Martins
2023-09-19  8:41       ` Muchun Song
2023-09-19  8:55         ` Joao Martins
2023-09-19  8:57           ` Muchun Song
2023-09-19 15:09             ` Joao Martins
2023-09-20  2:47               ` Muchun Song
2023-09-20 10:39                 ` Joao Martins
2023-09-21  1:42                   ` Muchun Song
2023-09-18 23:01 ` [PATCH v4 7/8] hugetlb: batch TLB flushes when freeing vmemmap Mike Kravetz
2023-09-18 23:02 ` [PATCH v4 8/8] hugetlb: batch TLB flushes when restoring vmemmap Mike Kravetz
2023-09-19  6:48   ` Muchun Song
2023-09-19 21:53     ` Mike Kravetz

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=20230922172824.GC224968@monkey \
    --to=mike.kravetz@oracle.com \
    --cc=21cnbao@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=david@redhat.com \
    --cc=duanxiongchun@bytedance.com \
    --cc=joao.m.martins@oracle.com \
    --cc=linmiaohe@huawei.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mhocko@suse.com \
    --cc=muchun.song@linux.dev \
    --cc=naoya.horiguchi@linux.dev \
    --cc=osalvador@suse.de \
    --cc=rientjes@google.com \
    --cc=songmuchun@bytedance.com \
    --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 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.