cgroups. And 'virsh numatune'
already provides that for the whole domain (we just don't have an API
to do that per memory).
-Original Message-
From: libvir-list-boun...@redhat.com On
Behalf Of Zhong, Luyao
Sent: Thursday, April 1, 2021 10:58 AM
To: Martin Kletzander ; Dani
r memory).
>-Original Message-
>From: libvir-list-boun...@redhat.com On
>Behalf Of Zhong, Luyao
>Sent: Thursday, April 1, 2021 10:58 AM
>To: Martin Kletzander ; Daniel P. Berrangé
>
>Cc: libvir-list@redhat.com
>Subject: RE: [libvirt][PATCH v4 0/3] introduce 'rest
>-Original Message-
>From: Martin Kletzander
>Sent: Wednesday, March 31, 2021 5:37 PM
>To: Zhong, Luyao
>Cc: Daniel P. Berrangé ; libvir-list@redhat.com
>Subject: Re: [libvirt][PATCH v4 0/3] introduce 'restrictive' mode in numatune
>
>On Wed, Mar 31, 2021 at
in numatune
On Tue, Mar 30, 2021 at 08:53:19AM +, Zhong, Luyao wrote:
-Original Message-
From: Martin Kletzander
Sent: Thursday, March 25, 2021 10:28 PM
To: Daniel P. Berrangé
Cc: Zhong, Luyao ; libvir-list@redhat.com
Subject: Re: [libvirt][PATCH v4 0/3] introduce 'restrictive' mode
>-Original Message-
>From: Martin Kletzander
>Sent: Wednesday, March 31, 2021 12:21 AM
>To: Zhong, Luyao
>Cc: Daniel P. Berrangé ; libvir-list@redhat.com
>Subject: Re: [libvirt][PATCH v4 0/3] introduce 'restrictive' mode in numatune
>
>On Tue, Mar 30, 2021 at
> > > From: Martin Kletzander
>> > > Sent: Thursday, March 25, 2021 4:46 AM
>> > > To: Daniel P. Berrangé
>> > > Cc: Zhong, Luyao ; libvir-list@redhat.com
>> > > Subject: Re: [libvirt][PATCH v4 0/3] introduce 'restrictive' mode
>> > &g
> -Original Message-
> From: Martin Kletzander
> Sent: Thursday, March 25, 2021 10:28 PM
> To: Daniel P. Berrangé
> Cc: Zhong, Luyao ; libvir-list@redhat.com
> Subject: Re: [libvirt][PATCH v4 0/3] introduce 'restrictive' mode in numatune
>
> On Thu, Mar 25,
Thursday, March 25, 2021 4:46 AM
> > To: Daniel P. Berrangé
> > Cc: Zhong, Luyao ; libvir-list@redhat.com
> > Subject: Re: [libvirt][PATCH v4 0/3] introduce 'restrictive' mode in
numatune
> >
> > On Tue, Mar 23, 2021 at 09:48:02AM +, Daniel P. Berrangé wrote:
>
; > > To: Daniel P. Berrangé
> > > Cc: Zhong, Luyao ; libvir-list@redhat.com
> > > Subject: Re: [libvirt][PATCH v4 0/3] introduce 'restrictive' mode in
> > > numatune
> > >
> > > On Tue, Mar 23, 2021 at 09:48:02AM +, Daniel P. Berrangé wrote:
&g
On Thu, Mar 25, 2021 at 09:11:02AM +, Zhong, Luyao wrote:
-Original Message-
From: Martin Kletzander
Sent: Thursday, March 25, 2021 4:46 AM
To: Daniel P. Berrangé
Cc: Zhong, Luyao ; libvir-list@redhat.com
Subject: Re: [libvirt][PATCH v4 0/3] introduce 'restrictive' mode
On Thu, Mar 25, 2021 at 08:36:17AM +, Daniel P. Berrangé wrote:
On Wed, Mar 24, 2021 at 09:46:23PM +0100, Martin Kletzander wrote:
On Tue, Mar 23, 2021 at 09:48:02AM +, Daniel P. Berrangé wrote:
> On Tue, Mar 23, 2021 at 10:59:02AM +0800, Luyao Zhong wrote:
> > Before this patch set,
> -Original Message-
> From: Martin Kletzander
> Sent: Thursday, March 25, 2021 4:46 AM
> To: Daniel P. Berrangé
> Cc: Zhong, Luyao ; libvir-list@redhat.com
> Subject: Re: [libvirt][PATCH v4 0/3] introduce 'restrictive' mode in numatune
>
> On Tue, Mar 23,
On Wed, Mar 24, 2021 at 09:46:23PM +0100, Martin Kletzander wrote:
> On Tue, Mar 23, 2021 at 09:48:02AM +, Daniel P. Berrangé wrote:
> > On Tue, Mar 23, 2021 at 10:59:02AM +0800, Luyao Zhong wrote:
> > > Before this patch set, numatune only has three memory modes:
> > > static, interleave and
On Tue, Mar 23, 2021 at 09:48:02AM +, Daniel P. Berrangé wrote:
On Tue, Mar 23, 2021 at 10:59:02AM +0800, Luyao Zhong wrote:
Before this patch set, numatune only has three memory modes:
static, interleave and prefered. These memory policies are
ultimately set by mbind() system call.
Memory
On Tue, Mar 23, 2021 at 10:59:02AM +0800, Luyao Zhong wrote:
> Before this patch set, numatune only has three memory modes:
> static, interleave and prefered. These memory policies are
> ultimately set by mbind() system call.
>
> Memory policy could be 'hard coded' into the kernel, but none of
>
Before this patch set, numatune only has three memory modes:
static, interleave and prefered. These memory policies are
ultimately set by mbind() system call.
Memory policy could be 'hard coded' into the kernel, but none of
above policies fit our requirment under this case. mbind() support
16 matches
Mail list logo
