From: Dave Hansen <dave.hansen@intel.com>
To: Nitesh Narayan Lal <nitesh@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, pbonzini@redhat.com, lcapitulino@redhat.com,
pagupta@redhat.com, wei.w.wang@intel.com,
yang.zhang.wz@gmail.com, riel@surriel.com, david@redhat.com,
mst@redhat.com, dodgen@google.com, konrad.wilk@oracle.com,
dhildenb@redhat.com, aarcange@redhat.com,
alexander.duyck@gmail.com, john.starks@microsoft.com,
mhocko@suse.com
Subject: Re: [RFC][Patch v11 1/2] mm: page_hinting: core infrastructure
Date: Thu, 11 Jul 2019 09:45:11 -0700 [thread overview]
Message-ID: <719ac813-01d7-7602-0951-6c90f1f7efc1@intel.com> (raw)
In-Reply-To: <fd49381e-cdfa-7ac9-e938-ac790995df24@redhat.com>
On 7/11/19 9:36 AM, Nitesh Narayan Lal wrote:
>>>>> +struct zone_free_area {
>>>>> + unsigned long *bitmap;
>>>>> + unsigned long base_pfn;
>>>>> + unsigned long end_pfn;
>>>>> + atomic_t free_pages;
>>>>> + unsigned long nbits;
>>>>> +} free_area[MAX_NR_ZONES];
>>>> Why do we need an extra data structure. What's wrong with putting
>>>> per-zone data in ... 'struct zone'?
>>> Will it be acceptable to add fields in struct zone, when they will only
>>> be used by page hinting?
>> Wait a sec... MAX_NR_ZONES the number of zone types not the maximum
>> number of *zones* in the system.
>>
>> Did you test this on a NUMA system?
> Yes, I tested it with a guest having 2 and 3 NUMA nodes.
How can this *possibly* have worked?
Won't each same-typed zone just use the same free_area[] entry since
zone_idx(zone1)==zone_idx(zone2) if zone1 and zone2 are (for example)
both ZONE_NORMAL?
next prev parent reply other threads:[~2019-07-11 16:45 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 19:51 [RFC][PATCH v11 0/2] mm: Support for page hinting Nitesh Narayan Lal
2019-07-10 19:51 ` [RFC][Patch v11 1/2] mm: page_hinting: core infrastructure Nitesh Narayan Lal
2019-07-10 20:45 ` Dave Hansen
2019-07-11 11:48 ` Nitesh Narayan Lal
2019-07-11 15:25 ` Nitesh Narayan Lal
2019-07-11 15:50 ` Nitesh Narayan Lal
2019-07-11 16:22 ` Dave Hansen
2019-07-11 16:36 ` Nitesh Narayan Lal
2019-07-11 16:45 ` Dave Hansen [this message]
2019-07-11 16:52 ` Nitesh Narayan Lal
2019-07-15 9:26 ` David Hildenbrand
2019-07-10 21:56 ` Alexander Duyck
2019-07-11 17:58 ` Nitesh Narayan Lal
2019-07-11 23:20 ` Alexander Duyck
2019-07-12 1:12 ` Nitesh Narayan Lal
2019-07-12 16:22 ` Alexander Duyck
2019-07-12 16:25 ` Nitesh Narayan Lal
2019-08-08 11:41 ` Nitesh Narayan Lal
2019-07-11 18:21 ` Dave Hansen
2019-07-15 9:33 ` David Hildenbrand
2019-07-15 14:40 ` David Hildenbrand
2019-07-10 19:51 ` [RFC][Patch v11 2/2] virtio-balloon: page_hinting: reporting to the host Nitesh Narayan Lal
2019-07-24 19:47 ` Michael S. Tsirkin
2019-07-24 19:56 ` David Hildenbrand
2019-07-24 20:10 ` Nitesh Narayan Lal
2019-07-24 20:06 ` Nitesh Narayan Lal
2019-07-10 19:53 ` [QEMU Patch] virtio-baloon: Support for page hinting Nitesh Narayan Lal
2019-07-10 20:17 ` Alexander Duyck
2019-07-11 12:03 ` Nitesh Narayan Lal
2019-07-11 8:49 ` Cornelia Huck
2019-07-11 11:13 ` Nitesh Narayan Lal
2019-07-11 18:55 ` Michael S. Tsirkin
2019-07-11 19:06 ` Nitesh Narayan Lal
2019-07-11 22:36 ` Alexander Duyck
2019-07-10 20:19 ` [RFC][PATCH v11 0/2] mm: " Dave Hansen
2019-07-11 11:37 ` Nitesh Narayan Lal
2019-07-10 23:40 ` Alexander Duyck
2019-07-11 11:30 ` Nitesh Narayan Lal
2019-07-11 14:58 ` Alexander Duyck
2019-07-11 15:03 ` Nitesh Narayan Lal
2019-07-11 15:08 ` Alexander Duyck
2019-07-11 15:19 ` Nitesh Narayan Lal
2019-07-11 17:01 ` Alexander Duyck
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=719ac813-01d7-7602-0951-6c90f1f7efc1@intel.com \
--to=dave.hansen@intel.com \
--cc=aarcange@redhat.com \
--cc=alexander.duyck@gmail.com \
--cc=david@redhat.com \
--cc=dhildenb@redhat.com \
--cc=dodgen@google.com \
--cc=john.starks@microsoft.com \
--cc=konrad.wilk@oracle.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@suse.com \
--cc=mst@redhat.com \
--cc=nitesh@redhat.com \
--cc=pagupta@redhat.com \
--cc=pbonzini@redhat.com \
--cc=riel@surriel.com \
--cc=wei.w.wang@intel.com \
--cc=yang.zhang.wz@gmail.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;
as well as URLs for NNTP newsgroup(s).