search for: oom_vballoon_pag

...e units. So each page is pointed to by @@ -36,6 +37,12 @@ */ #define VIRTIO_BALLOON_PAGES_PER_PAGE (unsigned)(PAGE_SIZE >> VIRTIO_BALLOON_PFN_SHIFT) #define VIRTIO_BALLOON_ARRAY_PFNS_MAX 256 +#define OOM_VBALLOON_DEFAULT_PAGES 256 +#define VIRTBALLOON_OOM_NOTIFY_PRIORITY 80 + +static int oom_vballoon_pages = OOM_VBALLOON_DEFAULT_PAGES; +module_param(oom_vballoon_pages, int, S_IRUSR | S_IWUSR); +MODULE_PARM_DESC(oom_vballoon_pages, "pages to free on OOM"); struct virtio_balloon { @@ -71,6 +78,9 @@ struct virtio_balloon /* Memory statistics */ int need_stats_update; struct virtio_...

...e units. So each page is pointed to by @@ -36,6 +37,12 @@ */ #define VIRTIO_BALLOON_PAGES_PER_PAGE (unsigned)(PAGE_SIZE >> VIRTIO_BALLOON_PFN_SHIFT) #define VIRTIO_BALLOON_ARRAY_PFNS_MAX 256 +#define OOM_VBALLOON_DEFAULT_PAGES 256 +#define VIRTBALLOON_OOM_NOTIFY_PRIORITY 80 + +static int oom_vballoon_pages = OOM_VBALLOON_DEFAULT_PAGES; +module_param(oom_vballoon_pages, int, S_IRUSR | S_IWUSR); +MODULE_PARM_DESC(oom_vballoon_pages, "pages to free on OOM"); struct virtio_balloon { @@ -71,6 +78,9 @@ struct virtio_balloon /* Memory statistics */ int need_stats_update; struct virtio_...

Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS runs out of memory and invokes OOM-killer. The balancing of

Excessive virtio_balloon inflation can cause invocation of OOM-killer, when Linux is under severe memory pressure. Various mechanisms are responsible for correct virtio_balloon memory management. Nevertheless it is often the case that these control tools does not have enough time to react on fast changing memory load. As a result OS runs out of memory and invokes OOM-killer. The balancing of

...nation of processes while there are > pages in the balloon. Now there is no way for virtio balloon driver to > free some memory at the last moment before some process will be get > killed by OOM-killer. This makes some amount of sense. But I suggest a few minor changes: > +static int oom_vballoon_pages = OOM_VBALLOON_DEFAULT_PAGES; > +module_param(oom_vballoon_pages, int, S_IRUSR | S_IWUSR); > +MODULE_PARM_DESC(oom_vballoon_pages, "pages to free on OOM"); Since this is already prefixed with "virtio_balloon." I suggest just calling it "oom_pages". > +stat...

...t the moment host does not expect guest to deflate before requests. So as a minimum, add a feature bit for this. what if you want a mix of mandatory and optional balooning? I guess we can use multiple balloons, is that the idea? > But I suggest a few minor changes: > > > +static int oom_vballoon_pages = OOM_VBALLOON_DEFAULT_PAGES; > > +module_param(oom_vballoon_pages, int, S_IRUSR | S_IWUSR); > > +MODULE_PARM_DESC(oom_vballoon_pages, "pages to free on OOM"); > > Since this is already prefixed with "virtio_balloon." I suggest just > calling it "oom...

...t the moment host does not expect guest to deflate before requests. So as a minimum, add a feature bit for this. what if you want a mix of mandatory and optional balooning? I guess we can use multiple balloons, is that the idea? > But I suggest a few minor changes: > > > +static int oom_vballoon_pages = OOM_VBALLOON_DEFAULT_PAGES; > > +module_param(oom_vballoon_pages, int, S_IRUSR | S_IWUSR); > > +MODULE_PARM_DESC(oom_vballoon_pages, "pages to free on OOM"); > > Since this is already prefixed with "virtio_balloon." I suggest just > calling it "oom...