From: Wenkuan Wang <wwk0817@gmail.com> To: Mina Almasry <almasrymina@google.com>, mike.kravetz@oracle.com Cc: shuah@kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-kselftest@vger.kernel.org, cgroups@vger.kernel.org, aneesh.kumar@linux.vnet.ibm.com Subject: Re: [PATCH v8 5/9] hugetlb: disable region_add file_region coalescing Date: Sun, 17 Nov 2019 19:03:16 +0800 [thread overview] Message-ID: <010d5a90-3ebf-30e5-8829-a61f01b6f620@gmail.com> (raw) In-Reply-To: <20191030013701.39647-5-almasrymina@google.com> On 10/30/19 9:36 AM, Mina Almasry wrote: > /* Must be called with resv->lock held. Calling this with count_only == true > * will count the number of pages to be added but will not modify the linked > - * list. > + * list. If regions_needed != NULL and count_only == true, then regions_needed > + * will indicate the number of file_regions needed in the cache to carry out to > + * add the regions for this range. > */ > static long add_reservation_in_range(struct resv_map *resv, long f, long t, Hi Mina, Would you please share which tree this patch set used? this patch 5/9 can't be applied with Linus's tree and add_reservation_in_range can't be found. Thanks Wenkuan > - bool count_only) > + long *regions_needed, bool count_only) > { > - long chg = 0; > + long add = 0; > struct list_head *head = &resv->regions; > + long last_accounted_offset = f; > struct file_region *rg = NULL, *trg = NULL, *nrg = NULL; > - /* Locate the region we are before or
next prev parent reply other threads:[~2019-11-17 11:03 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-10-30 1:36 [PATCH v8 1/9] hugetlb_cgroup: Add hugetlb_cgroup reservation counter Mina Almasry 2019-10-30 1:36 ` [PATCH v8 2/9] hugetlb_cgroup: add interface for charge/uncharge hugetlb reservations Mina Almasry 2019-11-08 0:57 ` Mike Kravetz 2019-11-08 23:48 ` Mina Almasry 2019-11-09 0:01 ` Mike Kravetz 2019-11-09 0:40 ` Mina Almasry 2019-11-09 0:46 ` Mike Kravetz 2019-11-25 20:26 ` Mina Almasry 2019-11-26 0:05 ` Mike Kravetz 2019-10-30 1:36 ` [PATCH v8 3/9] hugetlb_cgroup: add cgroup-v2 support Mina Almasry 2019-10-30 1:36 ` [PATCH v8 4/9] hugetlb_cgroup: add reservation accounting for private mappings Mina Almasry 2019-10-30 1:36 ` [PATCH v8 5/9] hugetlb: disable region_add file_region coalescing Mina Almasry 2019-11-01 23:23 ` Mike Kravetz 2019-11-04 21:04 ` Mina Almasry 2019-11-04 21:15 ` Mike Kravetz 2019-11-04 21:19 ` Mina Almasry 2019-11-17 11:03 ` Wenkuan Wang [this message] 2019-11-18 19:41 ` Mina Almasry 2019-10-30 1:36 ` [PATCH v8 6/9] hugetlb_cgroup: add accounting for shared mappings Mina Almasry 2019-10-30 1:36 ` [PATCH v8 7/9] hugetlb_cgroup: support noreserve mappings Mina Almasry 2019-10-30 1:37 ` [PATCH v8 8/9] hugetlb_cgroup: Add hugetlb_cgroup reservation tests Mina Almasry 2019-10-30 1:37 ` [PATCH v8 9/9] hugetlb_cgroup: Add hugetlb_cgroup reservation docs Mina Almasry 2019-11-07 23:42 ` [PATCH v8 1/9] hugetlb_cgroup: Add hugetlb_cgroup reservation counter Mike Kravetz 2019-11-08 23:35 ` Mina Almasry
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=010d5a90-3ebf-30e5-8829-a61f01b6f620@gmail.com \ --to=wwk0817@gmail.com \ --cc=almasrymina@google.com \ --cc=aneesh.kumar@linux.vnet.ibm.com \ --cc=cgroups@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-kselftest@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mike.kravetz@oracle.com \ --cc=shuah@kernel.org \ --subject='Re: [PATCH v8 5/9] hugetlb: disable region_add file_region coalescing' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).