From: Wei Wang <wei.w.wang@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Michal Hocko <mhocko@kernel.org>
Cc: virtio-dev@lists.oasis-open.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
virtualization <virtualization@lists.linux-foundation.org>,
KVM list <kvm@vger.kernel.org>, linux-mm <linux-mm@kvack.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
Paolo Bonzini <pbonzini@redhat.com>,
liliang.opensource@gmail.com, yang.zhang.wz@gmail.com,
quan.xu0@gmail.com, nilal@redhat.com,
Rik van Riel <riel@redhat.com>,
peterx@redhat.com
Subject: Re: [PATCH v35 1/5] mm: support to get hints of free page blocks
Date: Thu, 12 Jul 2018 10:21:58 +0800 [thread overview]
Message-ID: <5B46BB46.2080802@intel.com> (raw)
In-Reply-To: <CA+55aFwku2tDH4+rfaC67xc4-cEwSrXgnQaci=e2id5ZCRE9JQ@mail.gmail.com>
On 07/12/2018 12:23 AM, Linus Torvalds wrote:
> On Wed, Jul 11, 2018 at 2:21 AM Michal Hocko <mhocko@kernel.org> wrote:
>> We already have an interface for that. alloc_pages(GFP_NOWAIT, MAX_ORDER -1).
>> So why do we need any array based interface?
> That was actually my original argument in the original thread - that
> the only new interface people might want is one that just tells how
> many of those MAX_ORDER-1 pages there are.
>
> See the thread in v33 with the subject
>
> "[PATCH v33 1/4] mm: add a function to get free page blocks"
>
> and look for me suggesting just using
>
> #define GFP_MINFLAGS (__GFP_NORETRY | __GFP_NOWARN |
> __GFP_THISNODE | __GFP_NOMEMALLOC)
Would it be better to remove __GFP_THISNODE? We actually want to get all
the guest free pages (from all the nodes).
Best,
Wei
next prev parent reply other threads:[~2018-07-12 2:17 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-10 9:31 [PATCH v35 0/5] Virtio-balloon: support free page reporting Wei Wang
2018-07-10 9:31 ` [PATCH v35 1/5] mm: support to get hints of free page blocks Wei Wang
2018-07-10 10:16 ` Wang, Wei W
2018-07-10 17:33 ` Linus Torvalds
2018-07-11 1:28 ` Wei Wang
2018-07-11 1:44 ` Linus Torvalds
2018-07-11 9:21 ` Michal Hocko
2018-07-11 10:52 ` Wei Wang
2018-07-11 11:09 ` Michal Hocko
2018-07-11 13:55 ` Wang, Wei W
2018-07-11 14:38 ` Michal Hocko
2018-07-11 19:36 ` Michael S. Tsirkin
2018-07-11 16:23 ` Linus Torvalds
2018-07-12 2:21 ` Wei Wang [this message]
2018-07-12 2:30 ` Linus Torvalds
2018-07-12 2:52 ` Wei Wang
2018-07-12 8:13 ` Michal Hocko
2018-07-12 11:34 ` Wei Wang
2018-07-12 11:49 ` Michal Hocko
2018-07-13 0:33 ` Wei Wang
2018-07-12 13:12 ` Michal Hocko
2018-07-11 4:00 ` Michael S. Tsirkin
2018-07-11 4:04 ` Michael S. Tsirkin
2018-07-10 9:31 ` [PATCH v35 2/5] virtio-balloon: remove BUG() in init_vqs Wei Wang
2018-07-10 9:31 ` [PATCH v35 3/5] virtio-balloon: VIRTIO_BALLOON_F_FREE_PAGE_HINT Wei Wang
2018-07-10 9:31 ` [PATCH v35 4/5] mm/page_poison: expose page_poisoning_enabled to kernel modules Wei Wang
2018-07-10 9:31 ` [PATCH v35 5/5] virtio-balloon: VIRTIO_BALLOON_F_PAGE_POISON Wei Wang
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=5B46BB46.2080802@intel.com \
--to=wei.w.wang@intel.com \
--cc=akpm@linux-foundation.org \
--cc=kvm@vger.kernel.org \
--cc=liliang.opensource@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mhocko@kernel.org \
--cc=mst@redhat.com \
--cc=nilal@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=quan.xu0@gmail.com \
--cc=riel@redhat.com \
--cc=torvalds@linux-foundation.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.org \
--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).