On Tue, 10 Dec 2019 11:34:32 +0100
Markus Armbruster wrote:
> Eduardo Habkost writes:
>
> > +Markus
> >
> > On Tue, Dec 03, 2019 at 03:43:03PM +0100, Igor Mammedov wrote:
> >> On Tue, 3 Dec 2019 09:56:15 +0100
> >> Thomas Huth wrote:
> >>
> >> > On 02/12/2019 22.00, Eduardo Habkost wrote:
Eduardo Habkost writes:
> +Markus
>
> On Tue, Dec 03, 2019 at 03:43:03PM +0100, Igor Mammedov wrote:
>> On Tue, 3 Dec 2019 09:56:15 +0100
>> Thomas Huth wrote:
>>
>> > On 02/12/2019 22.00, Eduardo Habkost wrote:
>> > > On Mon, Dec 02, 2019 at 08:39:48AM +0100, Igor Mammedov wrote:
>> > >> On
+Markus
On Tue, Dec 03, 2019 at 03:43:03PM +0100, Igor Mammedov wrote:
> On Tue, 3 Dec 2019 09:56:15 +0100
> Thomas Huth wrote:
>
> > On 02/12/2019 22.00, Eduardo Habkost wrote:
> > > On Mon, Dec 02, 2019 at 08:39:48AM +0100, Igor Mammedov wrote:
> > >> On Fri, 29 Nov 2019 18:46:12 +0100
> > >
On Tue, Dec 03, 2019 at 09:56:15AM +0100, Thomas Huth wrote:
> On 02/12/2019 22.00, Eduardo Habkost wrote:
> > On Mon, Dec 02, 2019 at 08:39:48AM +0100, Igor Mammedov wrote:
> >> On Fri, 29 Nov 2019 18:46:12 +0100
> >> Paolo Bonzini wrote:
> >>
> >>> On 29/11/19 13:16, Igor Mammedov wrote:
>
On Tue, 3 Dec 2019 09:56:15 +0100
Thomas Huth wrote:
> On 02/12/2019 22.00, Eduardo Habkost wrote:
> > On Mon, Dec 02, 2019 at 08:39:48AM +0100, Igor Mammedov wrote:
> >> On Fri, 29 Nov 2019 18:46:12 +0100
> >> Paolo Bonzini wrote:
> >>
> >>> On 29/11/19 13:16, Igor Mammedov wrote:
>
On 02/12/2019 22.00, Eduardo Habkost wrote:
> On Mon, Dec 02, 2019 at 08:39:48AM +0100, Igor Mammedov wrote:
>> On Fri, 29 Nov 2019 18:46:12 +0100
>> Paolo Bonzini wrote:
>>
>>> On 29/11/19 13:16, Igor Mammedov wrote:
As for "-m", I'd make it just an alias that translates
-m/mem-path/me
On Mon, Dec 02, 2019 at 08:39:48AM +0100, Igor Mammedov wrote:
> On Fri, 29 Nov 2019 18:46:12 +0100
> Paolo Bonzini wrote:
>
> > On 29/11/19 13:16, Igor Mammedov wrote:
> > > As for "-m", I'd make it just an alias that translates
> > > -m/mem-path/mem-prealloc
> >
> > I think we should just d
On Fri, 29 Nov 2019 18:46:12 +0100
Paolo Bonzini wrote:
> On 29/11/19 13:16, Igor Mammedov wrote:
> > As for "-m", I'd make it just an alias that translates
> > -m/mem-path/mem-prealloc
>
> I think we should just deprecate -mem-path/-mem-prealloc in 5.0. CCing
> Thomas as mister deprecation.
On Fri, Nov 29, 2019 at 01:01:54PM +0100, Markus Armbruster wrote:
> Paolo Bonzini writes:
>
> > On 29/11/19 11:07, Igor Mammedov wrote:
> So user who wants something non trivial could override default
> non-numa behavior with
> -object memory-backend-file,id=mem,size=4G,mem-path
On 29/11/19 13:16, Igor Mammedov wrote:
> As for "-m", I'd make it just an alias that translates
> -m/mem-path/mem-prealloc
I think we should just deprecate -mem-path/-mem-prealloc in 5.0. CCing
Thomas as mister deprecation. :)
> combination to appropriate '-object' for '-machine memdev' consum
Paolo Bonzini writes:
> On 29/11/19 11:07, Igor Mammedov wrote:
So user who wants something non trivial could override default
non-numa behavior with
-object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on \
-machine memdev=mem
or use any other backend t
On Fri, 29 Nov 2019 11:11:09 +0100
Paolo Bonzini wrote:
> On 29/11/19 11:07, Igor Mammedov wrote:
> >>> So user who wants something non trivial could override default
> >>> non-numa behavior with
> >>> -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on \
> >>> -machine memd
On 29/11/19 11:07, Igor Mammedov wrote:
>>> So user who wants something non trivial could override default
>>> non-numa behavior with
>>> -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on \
>>> -machine memdev=mem
>>> or use any other backend that suits theirs needs.
>> Th
On Fri, 29 Nov 2019 00:31:32 +0400
Marc-André Lureau wrote:
> Hi
>
> On Thu, Nov 28, 2019 at 9:25 PM Igor Mammedov wrote:
> >
> > On Thu, 28 Nov 2019 18:15:18 +0400
> > Marc-André Lureau wrote:
> >
> > > Add an option to simplify shared memory / vhost-user setup.
> > >
> > > Currently, using
Hi
On Thu, Nov 28, 2019 at 9:25 PM Igor Mammedov wrote:
>
> On Thu, 28 Nov 2019 18:15:18 +0400
> Marc-André Lureau wrote:
>
> > Add an option to simplify shared memory / vhost-user setup.
> >
> > Currently, using vhost-user requires NUMA setup such as:
> > -m 4G -object memory-backend-file,id=me
On Thu, 28 Nov 2019 18:15:18 +0400
Marc-André Lureau wrote:
> Add an option to simplify shared memory / vhost-user setup.
>
> Currently, using vhost-user requires NUMA setup such as:
> -m 4G -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on
> -numa node,memdev=mem
>
> As th
+Igor
On Thu, Nov 28, 2019 at 06:15:18PM +0400, Marc-André Lureau wrote:
> Add an option to simplify shared memory / vhost-user setup.
>
> Currently, using vhost-user requires NUMA setup such as:
> -m 4G -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on
> -numa node,memdev=me
Add an option to simplify shared memory / vhost-user setup.
Currently, using vhost-user requires NUMA setup such as:
-m 4G -object memory-backend-file,id=mem,size=4G,mem-path=/dev/shm,share=on
-numa node,memdev=mem
As there is no other way to allocate shareable RAM, afaik.
-mem-shared aims to h
18 matches
Mail list logo