Re: [PATCH v1 00/12] virtio-mem: Expose device memory via multiple memslots

2021-11-07 Thread David Hildenbrand
On 07.11.21 11:21, Michael S. Tsirkin wrote: > On Sun, Nov 07, 2021 at 10:21:33AM +0100, David Hildenbrand wrote: >> Let's not focus on b), a) is the primary goal of this series: >> >> " >> a) Reduce the metadata overhead, including bitmap sizes inside KVM but >> also inside QEMU KVM code where pos

Re: [PATCH v1 00/12] virtio-mem: Expose device memory via multiple memslots

2021-11-07 Thread Michael S. Tsirkin
On Sun, Nov 07, 2021 at 10:21:33AM +0100, David Hildenbrand wrote: > Let's not focus on b), a) is the primary goal of this series: > > " > a) Reduce the metadata overhead, including bitmap sizes inside KVM but > also inside QEMU KVM code where possible. > " > > Because: > > " > For example, when

Re: [PATCH v1 00/12] virtio-mem: Expose device memory via multiple memslots

2021-11-07 Thread David Hildenbrand
On 07.11.21 09:14, Michael S. Tsirkin wrote: > On Tue, Nov 02, 2021 at 06:10:13PM +0100, David Hildenbrand wrote: >> On 02.11.21 18:06, Michael S. Tsirkin wrote: >>> On Tue, Nov 02, 2021 at 12:55:17PM +0100, David Hildenbrand wrote: On 02.11.21 12:35, Michael S. Tsirkin wrote: > On Tue, No

Re: [PATCH v1 00/12] virtio-mem: Expose device memory via multiple memslots

2021-11-07 Thread Michael S. Tsirkin
On Tue, Nov 02, 2021 at 06:10:13PM +0100, David Hildenbrand wrote: > On 02.11.21 18:06, Michael S. Tsirkin wrote: > > On Tue, Nov 02, 2021 at 12:55:17PM +0100, David Hildenbrand wrote: > >> On 02.11.21 12:35, Michael S. Tsirkin wrote: > >>> On Tue, Nov 02, 2021 at 09:33:55AM +0100, David Hildenbran

Re: [PATCH v1 00/12] virtio-mem: Expose device memory via multiple memslots

2021-11-02 Thread David Hildenbrand
On 02.11.21 18:06, Michael S. Tsirkin wrote: > On Tue, Nov 02, 2021 at 12:55:17PM +0100, David Hildenbrand wrote: >> On 02.11.21 12:35, Michael S. Tsirkin wrote: >>> On Tue, Nov 02, 2021 at 09:33:55AM +0100, David Hildenbrand wrote: On 01.11.21 23:15, Michael S. Tsirkin wrote: > On Wed, Oc

Re: [PATCH v1 00/12] virtio-mem: Expose device memory via multiple memslots

2021-11-02 Thread Michael S. Tsirkin
On Tue, Nov 02, 2021 at 12:55:17PM +0100, David Hildenbrand wrote: > On 02.11.21 12:35, Michael S. Tsirkin wrote: > > On Tue, Nov 02, 2021 at 09:33:55AM +0100, David Hildenbrand wrote: > >> On 01.11.21 23:15, Michael S. Tsirkin wrote: > >>> On Wed, Oct 27, 2021 at 02:45:19PM +0200, David Hildenbran

Re: [PATCH v1 00/12] virtio-mem: Expose device memory via multiple memslots

2021-11-02 Thread David Hildenbrand
On 02.11.21 12:35, Michael S. Tsirkin wrote: > On Tue, Nov 02, 2021 at 09:33:55AM +0100, David Hildenbrand wrote: >> On 01.11.21 23:15, Michael S. Tsirkin wrote: >>> On Wed, Oct 27, 2021 at 02:45:19PM +0200, David Hildenbrand wrote: This is the follow-up of [1], dropping auto-detection and vho

Re: [PATCH v1 00/12] virtio-mem: Expose device memory via multiple memslots

2021-11-02 Thread Michael S. Tsirkin
On Tue, Nov 02, 2021 at 09:33:55AM +0100, David Hildenbrand wrote: > On 01.11.21 23:15, Michael S. Tsirkin wrote: > > On Wed, Oct 27, 2021 at 02:45:19PM +0200, David Hildenbrand wrote: > >> This is the follow-up of [1], dropping auto-detection and vhost-user > >> changes from the initial RFC. > >>

Re: [PATCH v1 00/12] virtio-mem: Expose device memory via multiple memslots

2021-11-02 Thread David Hildenbrand
On 01.11.21 23:15, Michael S. Tsirkin wrote: > On Wed, Oct 27, 2021 at 02:45:19PM +0200, David Hildenbrand wrote: >> This is the follow-up of [1], dropping auto-detection and vhost-user >> changes from the initial RFC. >> >> Based-on: 20211011175346.15499-1-da...@redhat.com >> >> A virtio-mem devic

Re: [PATCH v1 00/12] virtio-mem: Expose device memory via multiple memslots

2021-11-01 Thread Michael S. Tsirkin
On Wed, Oct 27, 2021 at 02:45:19PM +0200, David Hildenbrand wrote: > This is the follow-up of [1], dropping auto-detection and vhost-user > changes from the initial RFC. > > Based-on: 20211011175346.15499-1-da...@redhat.com > > A virtio-mem device is represented by a single large RAM memory regio

[PATCH v1 00/12] virtio-mem: Expose device memory via multiple memslots

2021-10-27 Thread David Hildenbrand
This is the follow-up of [1], dropping auto-detection and vhost-user changes from the initial RFC. Based-on: 20211011175346.15499-1-da...@redhat.com A virtio-mem device is represented by a single large RAM memory region backed by a single large mmap. Right now, we map that complete memory region