From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: David Hildenbrand <david@redhat.com>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
virtio-dev@lists.oasis-open.org,
virtualization@lists.linux-foundation.org, kvm@vger.kernel.org,
Michal Hocko <mhocko@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"Michael S . Tsirkin" <mst@redhat.com>,
Sebastien Boeuf <sebastien.boeuf@intel.com>,
Samuel Ortiz <samuel.ortiz@intel.com>,
Robert Bradford <robert.bradford@intel.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
Alexander Duyck <alexander.h.duyck@linux.intel.com>,
Alexander Potapenko <glider@google.com>,
Alexander Viro <viro@zeniv.linux.org.uk>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Anthony Yznaga <anthony.yznaga@oracle.com>,
Dan Williams <dan.j.williams@intel.com>,
Dave Young <dyoung@redhat.com>,
Igor Mammedov <imammedo@redhat.com>,
Jason Wang <jasowang@redhat.com>,
Johannes Weiner <hannes@cmpxchg.org>,
Juergen Gross <jgross@suse.com>, Len Brown <lenb@kernel.org>,
Mel Gorman <mgorman@techsingularity.net>,
Michal Hocko <mhocko@suse.com>,
Mike Rapoport <rppt@linux.ibm.com>,
Oscar Salvador <osalvador@suse.com>,
Oscar Salvador <osalvador@suse.de>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Pavel Tatashin <pavel.tatashin@microsoft.com>,
Pingfan Liu <kernelfans@gmail.com>, Qian Cai <cai@lca.pw>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Stefan Hajnoczi <stefanha@redhat.com>,
Vlastimil Babka <vbabka@suse.cz>,
Wei Yang <richard.weiyang@gmail.com>
Subject: Re: [PATCH RFC v4 00/13] virtio-mem: paravirtualized memory
Date: Fri, 13 Dec 2019 12:15:56 -0800 (PST) [thread overview]
Message-ID: <20191213201556.GC26990@char.us.oracle.com> (raw)
In-Reply-To: <20191212171137.13872-1-david@redhat.com>
On Thu, Dec 12, 2019 at 06:11:24PM +0100, David Hildenbrand wrote:
> This series is based on latest linux-next. The patches are located at:
> https://github.com/davidhildenbrand/linux.git virtio-mem-rfc-v4
Heya!
Would there be by any chance a virtio-spec git tree somewhere?
..snip..
> --------------------------------------------------------------------------
> 5. Future work
> --------------------------------------------------------------------------
>
> The separate patches contain a lot of future work items. One of the next
> steps is to make memory unplug more likely to succeed - currently, there
> are no guarantees on how much memory can get unplugged again. I have
Or perhaps tell the caller why we can't and let them sort it out?
For example: "Application XYZ is mlocked. Can't offload'.
WARNING: multiple messages have this Message-ID (diff)
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: David Hildenbrand <david@redhat.com>
Cc: Oscar Salvador <osalvador@suse.com>,
Michal Hocko <mhocko@suse.com>,
Robert Bradford <robert.bradford@intel.com>,
"Michael S . Tsirkin" <mst@redhat.com>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Pingfan Liu <kernelfans@gmail.com>,
Luiz Capitulino <lcapitulino@redhat.com>,
linux-mm@kvack.org, Alexander Potapenko <glider@google.com>,
Alexander Duyck <alexander.h.duyck@linux.intel.com>,
virtio-dev@lists.oasis-open.org, kvm@vger.kernel.org,
Mike Rapoport <rppt@linux.ibm.com>,
Wei Yang <richard.weiyang@gmail.com>,
Anthony Yznaga <anthony.yznaga@oracle.com>,
Dave Young <dyoung@redhat.com>, Len Brown <lenb@kernel.org>,
Pavel Tatashin <pavel.tatashin@microsoft.com>,
Pavel Tatashin <pasha.tatashin@soleen.com>,
Anshuman Khandual <anshuman.khandual@arm.com>,
Qian Cai <cai@lca.pw>, Alexander Viro <viro@zeniv.linux.org.uk>,
Stefan Hajnoczi <stefanha@redhat.com>, Samuel Ortiz <samuel>
Subject: Re: [PATCH RFC v4 00/13] virtio-mem: paravirtualized memory
Date: Fri, 13 Dec 2019 12:15:56 -0800 (PST) [thread overview]
Message-ID: <20191213201556.GC26990@char.us.oracle.com> (raw)
In-Reply-To: <20191212171137.13872-1-david@redhat.com>
On Thu, Dec 12, 2019 at 06:11:24PM +0100, David Hildenbrand wrote:
> This series is based on latest linux-next. The patches are located at:
> https://github.com/davidhildenbrand/linux.git virtio-mem-rfc-v4
Heya!
Would there be by any chance a virtio-spec git tree somewhere?
..snip..
> --------------------------------------------------------------------------
> 5. Future work
> --------------------------------------------------------------------------
>
> The separate patches contain a lot of future work items. One of the next
> steps is to make memory unplug more likely to succeed - currently, there
> are no guarantees on how much memory can get unplugged again. I have
Or perhaps tell the caller why we can't and let them sort it out?
For example: "Application XYZ is mlocked. Can't offload'.
next prev parent reply other threads:[~2019-12-13 20:41 UTC|newest]
Thread overview: 117+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-12 17:11 [PATCH RFC v4 00/13] virtio-mem: paravirtualized memory David Hildenbrand
2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand
2019-12-12 17:11 ` [PATCH RFC v4 01/13] ACPI: NUMA: export pxm_to_node David Hildenbrand
2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand
2019-12-12 21:43 ` Rafael J. Wysocki
2019-12-13 9:41 ` David Hildenbrand
2019-12-13 9:41 ` David Hildenbrand
2019-12-13 9:41 ` [virtio-dev] " David Hildenbrand
2019-12-13 9:47 ` Rafael J. Wysocki
2019-12-13 9:47 ` Rafael J. Wysocki
2019-12-13 9:47 ` Rafael J. Wysocki
2019-12-12 17:11 ` David Hildenbrand
2019-12-12 17:11 ` [PATCH RFC v4 02/13] virtio-mem: Paravirtualized memory hotplug David Hildenbrand
2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand
2019-12-12 17:11 ` David Hildenbrand
2019-12-12 17:11 ` [PATCH RFC v4 03/13] virtio-mem: Paravirtualized memory hotunplug part 1 David Hildenbrand
2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand
2019-12-12 17:11 ` David Hildenbrand
2019-12-12 17:11 ` [PATCH RFC v4 04/13] mm: Export alloc_contig_range() / free_contig_range() David Hildenbrand
2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand
2019-12-12 17:11 ` David Hildenbrand
2019-12-12 17:11 ` [PATCH RFC v4 05/13] virtio-mem: Paravirtualized memory hotunplug part 2 David Hildenbrand
2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand
2019-12-12 17:11 ` David Hildenbrand
2019-12-12 17:11 ` [PATCH RFC v4 06/13] mm: Allow to offline unmovable PageOffline() pages via MEM_GOING_OFFLINE David Hildenbrand
2019-12-12 17:11 ` David Hildenbrand
2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand
2020-02-25 18:26 ` Alexander Duyck
2020-02-25 18:26 ` [virtio-dev] " Alexander Duyck
2020-02-25 18:26 ` Alexander Duyck
2020-02-25 18:49 ` David Hildenbrand
2020-02-25 18:49 ` [virtio-dev] " David Hildenbrand
2020-02-25 18:49 ` David Hildenbrand
2020-02-25 21:46 ` Alexander Duyck
2020-02-25 21:46 ` [virtio-dev] " Alexander Duyck
2020-02-25 21:46 ` Alexander Duyck
2020-02-25 22:19 ` David Hildenbrand
2020-02-25 22:19 ` [virtio-dev] " David Hildenbrand
2020-02-25 22:19 ` David Hildenbrand
2020-02-26 16:27 ` Alexander Duyck
2020-02-26 16:27 ` [virtio-dev] " Alexander Duyck
2020-02-26 16:27 ` Alexander Duyck
2019-12-12 17:11 ` [PATCH RFC v4 07/13] virtio-mem: Allow to offline partially unplugged memory blocks David Hildenbrand
2019-12-12 17:11 ` David Hildenbrand
2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand
2019-12-12 17:11 ` [PATCH RFC v4 08/13] mm/memory_hotplug: Introduce offline_and_remove_memory() David Hildenbrand
2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand
2020-02-25 14:11 ` Michal Hocko
2020-02-25 14:27 ` David Hildenbrand
2020-02-25 14:27 ` [virtio-dev] " David Hildenbrand
2020-03-02 12:48 ` Michal Hocko
2020-03-02 12:53 ` David Hildenbrand
2020-03-02 12:53 ` [virtio-dev] " David Hildenbrand
2019-12-12 17:11 ` David Hildenbrand
2019-12-12 17:11 ` [PATCH RFC v4 09/13] virtio-mem: Offline and remove completely unplugged memory blocks David Hildenbrand
2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand
2019-12-12 17:11 ` David Hildenbrand
2019-12-12 17:11 ` [PATCH RFC v4 10/13] virtio-mem: Better retry handling David Hildenbrand
2019-12-12 17:11 ` David Hildenbrand
2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand
2019-12-12 17:11 ` [PATCH RFC v4 11/13] mm/vmscan: Move count_vm_event(DROP_SLAB) into drop_slab() David Hildenbrand
2019-12-12 17:11 ` David Hildenbrand
2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand
2020-02-25 14:13 ` Michal Hocko
2019-12-12 17:11 ` [PATCH RFC v4 12/13] mm/vmscan: Export drop_slab() and drop_slab_node() David Hildenbrand
2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand
2020-02-25 14:58 ` Michal Hocko
2020-02-25 15:09 ` David Hildenbrand
2020-02-25 15:09 ` [virtio-dev] " David Hildenbrand
2020-02-25 17:06 ` Michal Hocko
2020-02-25 17:23 ` David Hildenbrand
2020-02-25 17:23 ` [virtio-dev] " David Hildenbrand
2019-12-12 17:11 ` David Hildenbrand
2019-12-12 17:11 ` [PATCH RFC v4 13/13] virtio-mem: Drop slab objects when unplug continues to fail David Hildenbrand
2019-12-12 17:11 ` [virtio-dev] " David Hildenbrand
2019-12-12 17:11 ` David Hildenbrand
2019-12-13 20:15 ` Konrad Rzeszutek Wilk [this message]
2019-12-13 20:15 ` [PATCH RFC v4 00/13] virtio-mem: paravirtualized memory Konrad Rzeszutek Wilk
2019-12-16 11:03 ` David Hildenbrand
2019-12-16 11:03 ` David Hildenbrand
2019-12-16 11:03 ` [virtio-dev] " David Hildenbrand
2019-12-24 6:58 ` teawater
2019-12-24 9:28 ` David Hildenbrand
2019-12-24 9:28 ` [virtio-dev] " David Hildenbrand
2019-12-24 9:28 ` David Hildenbrand
2020-01-09 13:48 ` David Hildenbrand
2020-01-09 13:48 ` [virtio-dev] " David Hildenbrand
2020-01-29 9:41 ` David Hildenbrand
2020-01-29 9:41 ` [virtio-dev] " David Hildenbrand
2020-01-29 9:41 ` David Hildenbrand
2020-02-25 9:58 ` David Hildenbrand
2020-02-25 9:58 ` [virtio-dev] " David Hildenbrand
2020-02-25 9:58 ` David Hildenbrand
2020-06-05 8:55 ` Alex Shi
2020-06-05 8:55 ` Alex Shi
2020-06-05 9:08 ` David Hildenbrand
2020-06-05 9:08 ` [virtio-dev] " David Hildenbrand
2020-06-05 9:08 ` David Hildenbrand
2020-06-05 9:36 ` David Hildenbrand
2020-06-05 9:36 ` [virtio-dev] " David Hildenbrand
2020-06-05 9:36 ` David Hildenbrand
2020-06-05 10:05 ` David Hildenbrand
2020-06-05 10:05 ` [virtio-dev] " David Hildenbrand
2020-06-05 10:05 ` David Hildenbrand
2020-06-05 10:46 ` Alex Shi
2020-06-05 10:46 ` Alex Shi
2020-06-05 12:18 ` David Hildenbrand
2020-06-05 12:18 ` [virtio-dev] " David Hildenbrand
2020-06-05 12:18 ` David Hildenbrand
2020-06-09 3:05 ` Alex Shi
2020-06-09 3:05 ` Alex Shi
2020-06-05 10:08 ` Alex Shi
2020-06-05 10:08 ` Alex Shi
2020-06-05 10:06 ` Alex Shi
2020-06-05 10:06 ` Alex Shi
2020-01-09 13:48 ` David Hildenbrand
-- strict thread matches above, loose matches on Subject: below --
2019-12-12 17:11 David Hildenbrand
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=20191213201556.GC26990@char.us.oracle.com \
--to=konrad.wilk@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=alexander.h.duyck@linux.intel.com \
--cc=anshuman.khandual@arm.com \
--cc=anthony.yznaga@oracle.com \
--cc=cai@lca.pw \
--cc=dan.j.williams@intel.com \
--cc=david@redhat.com \
--cc=dyoung@redhat.com \
--cc=glider@google.com \
--cc=hannes@cmpxchg.org \
--cc=imammedo@redhat.com \
--cc=jasowang@redhat.com \
--cc=jgross@suse.com \
--cc=kernelfans@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=lcapitulino@redhat.com \
--cc=lenb@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=mhocko@suse.com \
--cc=mst@redhat.com \
--cc=osalvador@suse.com \
--cc=osalvador@suse.de \
--cc=pasha.tatashin@soleen.com \
--cc=pavel.tatashin@microsoft.com \
--cc=richard.weiyang@gmail.com \
--cc=rjw@rjwysocki.net \
--cc=robert.bradford@intel.com \
--cc=rppt@linux.ibm.com \
--cc=samuel.ortiz@intel.com \
--cc=sebastien.boeuf@intel.com \
--cc=stefanha@redhat.com \
--cc=vbabka@suse.cz \
--cc=viro@zeniv.linux.org.uk \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtualization@lists.linux-foundation.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.