Re: [RFC PATCH v5 23/26] util: Add iova_tree_alloc

2021-11-22 Thread Peter Xu
Hi, Eugenio, Sorry for the super late response. On Fri, Oct 29, 2021 at 08:35:22PM +0200, Eugenio Pérez wrote: [...] > +int iova_tree_alloc(IOVATree *tree, DMAMap *map, hwaddr iova_begin, > +hwaddr iova_last) > +{ > +struct IOVATreeAllocArgs args = { > +.new_size

Re: [RFC PATCH v5 23/26] util: Add iova_tree_alloc

2021-11-22 Thread Eugenio Perez Martin
On Tue, Nov 23, 2021 at 7:57 AM Peter Xu wrote: > > Hi, Eugenio, > > Sorry for the super late response. > No problem! > On Fri, Oct 29, 2021 at 08:35:22PM +0200, Eugenio Pérez wrote: > > [...] > > > +int iova_tree_alloc(IOVATree *tree, DMAMap *map, hwaddr iova_begin, > > +hwa

[PATCH v4 1/3] migration/dirtyrate: implement vCPU dirtyrate calculation periodically

2021-11-22 Thread huangy81
From: Hyman Huang(黄勇) Introduce the third method GLOBAL_DIRTY_LIMIT of dirty tracking for calculate dirtyrate periodly for dirty restraint. Implement thread for calculate dirtyrate periodly, which will be used for dirty restraint. Add dirtylimit.h to introduce the util function for dirty limit

[PATCH v4 2/3] cpu-throttle: implement vCPU throttle

2021-11-22 Thread huangy81
From: Hyman Huang(黄勇) Impose dirty restraint on vCPU by kicking it and sleep as the auto-converge does during migration, but just kick the specified vCPU instead, not all vCPUs of vm. Start a thread to track the dirtylimit status and adjust the throttle pencentage dynamically depend on current a

[PATCH v4 3/3] cpus-common: implement dirty limit on vCPU

2021-11-22 Thread huangy81
From: Hyman Huang(黄勇) Implement dirtyrate calculation periodically basing on dirty-ring and throttle vCPU until it reachs the quota dirtyrate given by user. Introduce qmp commands set-dirty-limit/cancel-dirty-limit to set/cancel dirty limit on vCPU. Signed-off-by: Hyman Huang(黄勇) --- cpus-com

[PATCH v4 0/3] support dirty restraint on vCPU

2021-11-22 Thread huangy81
From: Hyman Huang(黄勇) v4: - rebase on master - modify the following points according to the advice given by Markus 1. move the defination into migration.json 2. polish the comments of set-dirty-limit 3. do the syntax check and change dirty rate to dirty page rate Thanks for the carefule re

<    1   2   3