On Tue, 2 Jul 2013 21:47:03 +0200
Pavel Machek wrote:
> On Tue 2013-07-02 11:06:28, Luiz Capitulino wrote:
> > On Mon, 1 Jul 2013 10:51:03 +0200
> > Pavel Machek wrote:
> >
> > > Hi!
> > >
> > > > diff --git a/Documentation/cgroups/mem
On Tue, 2 Jul 2013 10:24:09 -0700
Anton Vorontsov wrote:
> > Honestly, what Andrew suggested is the best design for me: apps
> > are notified on all events but the event name is sent to the application.
>
> I am fine with this approach (or any other, I'm really indifferent to the
> API itself
On Mon, 1 Jul 2013 10:51:03 +0200
Pavel Machek wrote:
> Hi!
>
> > diff --git a/Documentation/cgroups/memory.txt
> > b/Documentation/cgroups/memory.txt
> > index ddf4f93..3c589cf 100644
> > --- a/Documentation/cgroups/memory.txt
> > +++ b/Documentation/cgroups/memory.txt
> > @@ -807,12 +807,14
On Fri, 28 Jun 2013 17:56:37 -0700
Anton Vorontsov wrote:
> On Fri, Jun 28, 2013 at 03:44:02PM -0400, Luiz Capitulino wrote:
> > > Why can't you use poll() and demultiplex the events? Check if there is an
> > > event in the crit fd, and if there is, then jus
On Tue, 2 Jul 2013 10:24:09 -0700
Anton Vorontsov an...@enomsg.org wrote:
Honestly, what Andrew suggested is the best design for me: apps
are notified on all events but the event name is sent to the application.
I am fine with this approach (or any other, I'm really indifferent to the
API
On Tue, 2 Jul 2013 21:47:03 +0200
Pavel Machek pa...@ucw.cz wrote:
On Tue 2013-07-02 11:06:28, Luiz Capitulino wrote:
On Mon, 1 Jul 2013 10:51:03 +0200
Pavel Machek pa...@ucw.cz wrote:
Hi!
diff --git a/Documentation/cgroups/memory.txt
b/Documentation/cgroups/memory.txt
On Fri, 28 Jun 2013 17:56:37 -0700
Anton Vorontsov an...@enomsg.org wrote:
On Fri, Jun 28, 2013 at 03:44:02PM -0400, Luiz Capitulino wrote:
Why can't you use poll() and demultiplex the events? Check if there is an
event in the crit fd, and if there is, then just ignore all the rest
On Mon, 1 Jul 2013 10:51:03 +0200
Pavel Machek pa...@ucw.cz wrote:
Hi!
diff --git a/Documentation/cgroups/memory.txt
b/Documentation/cgroups/memory.txt
index ddf4f93..3c589cf 100644
--- a/Documentation/cgroups/memory.txt
+++ b/Documentation/cgroups/memory.txt
@@ -807,12 +807,14 @@
On Fri, 28 Jun 2013 11:55:47 -0700
Anton Vorontsov wrote:
> On Fri, Jun 28, 2013 at 02:45:07PM -0400, Luiz Capitulino wrote:
> > On Fri, 28 Jun 2013 10:09:17 -0700
> > Anton Vorontsov wrote:
> >
> > > So, I would now argue that the current scheme is perfectly OK a
On Fri, 28 Jun 2013 11:45:47 -0700
Anton Vorontsov wrote:
> On Fri, Jun 28, 2013 at 02:25:58PM -0400, Luiz Capitulino wrote:
> > > > > That's how it's expected to work, because on strict mode you're
> > > > > notified
> > > > > for the level you
On Fri, 28 Jun 2013 10:09:17 -0700
Anton Vorontsov wrote:
> So, I would now argue that the current scheme is perfectly OK and can do
> everything you can do with the "strict" one,
I forgot commenting this bit. This is not true, because I don't want a
low fd to be notified on critical level. The
On Fri, 28 Jun 2013 10:09:17 -0700
Anton Vorontsov wrote:
> On Fri, Jun 28, 2013 at 09:57:22AM -0700, Anton Vorontsov wrote:
> > On Fri, Jun 28, 2013 at 10:00:27AM -0400, Luiz Capitulino wrote:
> > > On Thu, 27 Jun 2013 22:07:12 -0700
> > > Anton Vorontsov wrote:
&g
On Thu, 27 Jun 2013 22:07:12 -0700
Anton Vorontsov wrote:
> On Thu, Jun 27, 2013 at 09:34:11PM -0700, Anton Vorontsov wrote:
> > ... we can add the strict mode and deprecate the
> > "filtering" -- basically we'll implement the idea of requiring that
> > userspace registers a separate fd for each
On Thu, 27 Jun 2013 21:34:11 -0700
Anton Vorontsov wrote:
> On Thu, Jun 27, 2013 at 06:13:53PM -0700, Andrew Morton wrote:
> > On Thu, 27 Jun 2013 17:58:53 -0700 Anton Vorontsov wrote:
> > > Current frequency is 1/(2MB). Suppose we ended up scanning the whole
> > > memory on a 2GB host, this
On Thu, 27 Jun 2013 21:34:11 -0700
Anton Vorontsov an...@enomsg.org wrote:
On Thu, Jun 27, 2013 at 06:13:53PM -0700, Andrew Morton wrote:
On Thu, 27 Jun 2013 17:58:53 -0700 Anton Vorontsov an...@enomsg.org wrote:
Current frequency is 1/(2MB). Suppose we ended up scanning the whole
memory
On Thu, 27 Jun 2013 22:07:12 -0700
Anton Vorontsov an...@enomsg.org wrote:
On Thu, Jun 27, 2013 at 09:34:11PM -0700, Anton Vorontsov wrote:
... we can add the strict mode and deprecate the
filtering -- basically we'll implement the idea of requiring that
userspace registers a separate fd
On Fri, 28 Jun 2013 10:09:17 -0700
Anton Vorontsov an...@enomsg.org wrote:
On Fri, Jun 28, 2013 at 09:57:22AM -0700, Anton Vorontsov wrote:
On Fri, Jun 28, 2013 at 10:00:27AM -0400, Luiz Capitulino wrote:
On Thu, 27 Jun 2013 22:07:12 -0700
Anton Vorontsov an...@enomsg.org wrote
On Fri, 28 Jun 2013 10:09:17 -0700
Anton Vorontsov an...@enomsg.org wrote:
So, I would now argue that the current scheme is perfectly OK and can do
everything you can do with the strict one,
I forgot commenting this bit. This is not true, because I don't want a
low fd to be notified on
On Fri, 28 Jun 2013 11:45:47 -0700
Anton Vorontsov an...@enomsg.org wrote:
On Fri, Jun 28, 2013 at 02:25:58PM -0400, Luiz Capitulino wrote:
That's how it's expected to work, because on strict mode you're
notified
for the level you registered for. So apps registering for critical
On Fri, 28 Jun 2013 11:55:47 -0700
Anton Vorontsov an...@enomsg.org wrote:
On Fri, Jun 28, 2013 at 02:45:07PM -0400, Luiz Capitulino wrote:
On Fri, 28 Jun 2013 10:09:17 -0700
Anton Vorontsov an...@enomsg.org wrote:
So, I would now argue that the current scheme is perfectly OK and can
On Thu, 27 Jun 2013 11:26:16 +0200
Michal Hocko wrote:
> On Wed 26-06-13 23:17:12, Luiz Capitulino wrote:
> > Currently, an eventfd is notified for the level it's registered for
> > _plus_ higher levels.
> >
> > This is a problem if an application wants to impl
On Thu, 27 Jun 2013 11:26:16 +0200
Michal Hocko mho...@suse.cz wrote:
On Wed 26-06-13 23:17:12, Luiz Capitulino wrote:
Currently, an eventfd is notified for the level it's registered for
_plus_ higher levels.
This is a problem if an application wants to implement different
actions
it registered for. This new mode is optional,
by default we still notify eventfds on higher levels too.
Signed-off-by: Luiz Capitulino
---
o v2
- Improve documentation
- Use a bit to store mode instead of a bool
- Minor changelog changes
Documentation/cgroups/memory.txt | 26
On Wed, 26 Jun 2013 10:08:27 +0200
Michal Hocko wrote:
> On Tue 25-06-13 17:51:29, Luiz Capitulino wrote:
> > Currently, applications are notified for the level they registered for
> > _plus_ higher levels.
> >
> > This is a problem if the application wants to impl
On Wed, 26 Jun 2013 17:20:40 +0900
Minchan Kim wrote:
> Hello Michal,
>
> On Wed, Jun 26, 2013 at 09:59:21AM +0200, Michal Hocko wrote:
> > On Wed 26-06-13 16:50:51, Minchan Kim wrote:
> > > On Tue, Jun 25, 2013 at 05:51:29PM -0400, Luiz Capitulino wrote:
> &g
On Tue, 25 Jun 2013 21:03:31 -0700
Anton Vorontsov wrote:
> On Tue, Jun 25, 2013 at 05:51:29PM -0400, Luiz Capitulino wrote:
> > Currently, applications are notified for the level they registered for
> > _plus_ higher levels.
> >
> > This is a problem if the app
On Tue, 25 Jun 2013 21:03:31 -0700
Anton Vorontsov an...@enomsg.org wrote:
On Tue, Jun 25, 2013 at 05:51:29PM -0400, Luiz Capitulino wrote:
Currently, applications are notified for the level they registered for
_plus_ higher levels.
This is a problem if the application wants
On Wed, 26 Jun 2013 17:20:40 +0900
Minchan Kim minc...@kernel.org wrote:
Hello Michal,
On Wed, Jun 26, 2013 at 09:59:21AM +0200, Michal Hocko wrote:
On Wed 26-06-13 16:50:51, Minchan Kim wrote:
On Tue, Jun 25, 2013 at 05:51:29PM -0400, Luiz Capitulino wrote:
Currently, applications
On Wed, 26 Jun 2013 10:08:27 +0200
Michal Hocko mho...@suse.cz wrote:
On Tue 25-06-13 17:51:29, Luiz Capitulino wrote:
Currently, applications are notified for the level they registered for
_plus_ higher levels.
This is a problem if the application wants to implement different
actions
it registered for. This new mode is optional,
by default we still notify eventfds on higher levels too.
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
o v2
- Improve documentation
- Use a bit to store mode instead of a bool
- Minor changelog changes
Documentation/cgroups/memory.txt | 26
On Wed, 26 Jun 2013 10:12:15 +0900
Hyunhee Kim wrote:
> Please see "[PATCH v3] memcg: event control at vmpressure". mail
> thread. (and also the thread I sent last Saturday.)
> There was discussion on this mode not sending lower events when "level
> != ev->level".
The new argument this patch
. By default we still notify
on higher levels.
Signed-off-by: Luiz Capitulino
---
PS: I'm following the discussion on the event storm problem, but I believe
strict mode is orthogonal to what has been suggested (although the
patches conflict)
Documentation/cgroups/memory.txt | 10
. By default we still notify
on higher levels.
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
PS: I'm following the discussion on the event storm problem, but I believe
strict mode is orthogonal to what has been suggested (although the
patches conflict)
Documentation/cgroups
On Wed, 26 Jun 2013 10:12:15 +0900
Hyunhee Kim hyunhee@samsung.com wrote:
Please see [PATCH v3] memcg: event control at vmpressure. mail
thread. (and also the thread I sent last Saturday.)
There was discussion on this mode not sending lower events when level
!= ev-level.
The new argument
On Wed, 5 Jun 2013 21:18:37 -0400
Luiz Capitulino wrote:
> The balloon_page_dequeue() function can return NULL. If it does for
> the first page being freed, then leak_balloon() will create a
> scatter list with len=0. Which in turn seems to generate an invalid
> virtio request.
>
On Wed, 5 Jun 2013 21:18:37 -0400
Luiz Capitulino lcapitul...@redhat.com wrote:
The balloon_page_dequeue() function can return NULL. If it does for
the first page being freed, then leak_balloon() will create a
scatter list with len=0. Which in turn seems to generate an invalid
virtio request
On Thu, 6 Jun 2013 11:13:58 -0300
Rafael Aquini wrote:
> On Wed, Jun 05, 2013 at 09:18:37PM -0400, Luiz Capitulino wrote:
> > The balloon_page_dequeue() function can return NULL. If it does for
> > the first page being freed, then leak_balloon() will create a
> > scatter l
On Thu, 6 Jun 2013 11:13:58 -0300
Rafael Aquini aqu...@redhat.com wrote:
On Wed, Jun 05, 2013 at 09:18:37PM -0400, Luiz Capitulino wrote:
The balloon_page_dequeue() function can return NULL. If it does for
the first page being freed, then leak_balloon() will create a
scatter list with len
, such an invalid virtio request will cause errors in QEMU and
fill_balloon() also performs the same check implemented by this commit.
Signed-off-by: Luiz Capitulino
Acked-by: Rafael Aquini
---
o v2
- Improve changelog
drivers/virtio/virtio_balloon.c | 3 ++-
1 file changed, 2 insertions(+), 1
On Wed, 5 Jun 2013 18:24:49 -0300
Rafael Aquini wrote:
> On Wed, Jun 05, 2013 at 05:10:31PM -0400, Luiz Capitulino wrote:
> > The balloon_page_dequeue() function can return NULL. If it does for
> > the first page being freed, then leak_balloon() will create a
> > scatter l
The balloon_page_dequeue() function can return NULL. If it does for
the first page being freed, then leak_balloon() will create a
scatter list with len=0. Which in turn seems to generate an invalid
virtio request.
Signed-off-by: Luiz Capitulino
---
PS: I didn't get this in practice. I found
The balloon_page_dequeue() function can return NULL. If it does for
the first page being freed, then leak_balloon() will create a
scatter list with len=0. Which in turn seems to generate an invalid
virtio request.
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
PS: I didn't get
On Wed, 5 Jun 2013 18:24:49 -0300
Rafael Aquini aqu...@redhat.com wrote:
On Wed, Jun 05, 2013 at 05:10:31PM -0400, Luiz Capitulino wrote:
The balloon_page_dequeue() function can return NULL. If it does for
the first page being freed, then leak_balloon() will create a
scatter list with len
, such an invalid virtio request will cause errors in QEMU and
fill_balloon() also performs the same check implemented by this commit.
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
Acked-by: Rafael Aquini aqu...@redhat.com
---
o v2
- Improve changelog
drivers/virtio/virtio_balloon.c | 3 ++-
1
On Thu, 16 May 2013 16:56:34 -0400
Sasha Levin wrote:
> On 05/09/2013 10:53 AM, Luiz Capitulino wrote:
> > Hi,
> >
> > This series is a respin of automatic ballooning support I started
> > working on last year. Patch 2/2 contains all relevant technical
> > det
On Thu, 16 May 2013 16:56:34 -0400
Sasha Levin sasha.le...@oracle.com wrote:
On 05/09/2013 10:53 AM, Luiz Capitulino wrote:
Hi,
This series is a respin of automatic ballooning support I started
working on last year. Patch 2/2 contains all relevant technical
details and performance
Commit 6501320311664e11ad5489fedb17ea1f817c2617 dropped the rpm spec as a
prerequisite for the binrpm-pkg target but forgot to update $< usage,
which causes the rule to break.
This commit fixes that by replacing $< with the spec name.
Signed-off-by: Luiz Capitulino
---
scripts/package/Ma
Commit 6501320311664e11ad5489fedb17ea1f817c2617 dropped the rpm spec as a
prerequisite for the binrpm-pkg target but forgot to update $ usage,
which causes the rule to break.
This commit fixes that by replacing $ with the spec name.
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
On Mon, 13 May 2013 22:02:50 +0300
"Michael S. Tsirkin" wrote:
> On Mon, May 13, 2013 at 02:25:11PM -0400, Luiz Capitulino wrote:
> > On Mon, 13 May 2013 11:34:41 -0300
> > Rafael Aquini wrote:
> >
> > > You're right, and the host's member is used t
On Mon, 13 May 2013 11:34:41 -0300
Rafael Aquini wrote:
> You're right, and the host's member is used to communicate the configured size
> to guest's balloon device, however, by not changing it when the shrinker
> causes
> the balloon to deflate will make the balloon thread to be woken up
On Sun, 12 May 2013 21:49:34 +0300
"Michael S. Tsirkin" wrote:
> On Sun, May 12, 2013 at 12:36:09PM -0400, Rik van Riel wrote:
> > On 05/12/2013 10:30 AM, Michael S. Tsirkin wrote:
> > >On Thu, May 09, 2013 at 10:53:49AM -0400, Luiz Capitulino wrote:
> &g
On Sun, 12 May 2013 21:49:34 +0300
Michael S. Tsirkin m...@redhat.com wrote:
On Sun, May 12, 2013 at 12:36:09PM -0400, Rik van Riel wrote:
On 05/12/2013 10:30 AM, Michael S. Tsirkin wrote:
On Thu, May 09, 2013 at 10:53:49AM -0400, Luiz Capitulino wrote:
Automatic ballooning consists
On Mon, 13 May 2013 11:34:41 -0300
Rafael Aquini aqu...@redhat.com wrote:
You're right, and the host's member is used to communicate the configured size
to guest's balloon device, however, by not changing it when the shrinker
causes
the balloon to deflate will make the balloon thread to be
On Mon, 13 May 2013 22:02:50 +0300
Michael S. Tsirkin m...@redhat.com wrote:
On Mon, May 13, 2013 at 02:25:11PM -0400, Luiz Capitulino wrote:
On Mon, 13 May 2013 11:34:41 -0300
Rafael Aquini aqu...@redhat.com wrote:
You're right, and the host's member is used to communicate
On Fri, 10 May 2013 09:20:46 -0400
Luiz Capitulino wrote:
> On Thu, 9 May 2013 18:15:19 -0300
> Rafael Aquini wrote:
>
> > On Thu, May 09, 2013 at 10:53:49AM -0400, Luiz Capitulino wrote:
> > > Automatic ballooning consists of dynamically adjusting the guest's
> >
On Thu, 9 May 2013 18:15:19 -0300
Rafael Aquini wrote:
> On Thu, May 09, 2013 at 10:53:49AM -0400, Luiz Capitulino wrote:
> > Automatic ballooning consists of dynamically adjusting the guest's
> > balloon according to memory pressure in the host and in the guest.
> >
>
On Thu, 9 May 2013 18:03:09 -0300
Rafael Aquini wrote:
> On Thu, May 09, 2013 at 10:53:48AM -0400, Luiz Capitulino wrote:
> > This commit moves the balloon_lock mutex out of the fill_balloon()
> > and leak_balloon() functions to their callers.
> >
> > The reason for t
On Thu, 9 May 2013 18:03:09 -0300
Rafael Aquini aqu...@redhat.com wrote:
On Thu, May 09, 2013 at 10:53:48AM -0400, Luiz Capitulino wrote:
This commit moves the balloon_lock mutex out of the fill_balloon()
and leak_balloon() functions to their callers.
The reason for this change
On Thu, 9 May 2013 18:15:19 -0300
Rafael Aquini aqu...@redhat.com wrote:
On Thu, May 09, 2013 at 10:53:49AM -0400, Luiz Capitulino wrote:
Automatic ballooning consists of dynamically adjusting the guest's
balloon according to memory pressure in the host and in the guest.
This commit
On Fri, 10 May 2013 09:20:46 -0400
Luiz Capitulino lcapitul...@redhat.com wrote:
On Thu, 9 May 2013 18:15:19 -0300
Rafael Aquini aqu...@redhat.com wrote:
On Thu, May 09, 2013 at 10:53:49AM -0400, Luiz Capitulino wrote:
Automatic ballooning consists of dynamically adjusting the guest's
semantics.
Signed-off-by: Luiz Capitulino
---
drivers/virtio/virtio_balloon.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/virtio/virtio_balloon.c b/drivers/virtio/virtio_balloon.c
index bd3ae32..9d5fe2b 100644
--- a/drivers/virtio/virtio_balloon.c
+++ b
1079847 1616367
4543 953289 1635379
5642 913237 1514000
Auto-ballooning enabled:
RUN TIME(s) SWAP IN SWAP OUT
1629 901 12537
2624 981 18506
3626 573 9085
4631 2250 42534
5627 1610 20808
Signed-off-by: Luiz
the guest memory down, say from 1G to 256MB
6. Generate some pressure in the guest, say a kernel build with -j16
Any feedback is appreciated!
Luiz Capitulino (2):
virtio_balloon: move balloon_lock mutex to callers
virtio_balloon: auto-ballooning support
drivers/virtio/virtio_balloon.c
the guest memory down, say from 1G to 256MB
6. Generate some pressure in the guest, say a kernel build with -j16
Any feedback is appreciated!
Luiz Capitulino (2):
virtio_balloon: move balloon_lock mutex to callers
virtio_balloon: auto-ballooning support
drivers/virtio/virtio_balloon.c
1079847 1616367
4543 953289 1635379
5642 913237 1514000
Auto-ballooning enabled:
RUN TIME(s) SWAP IN SWAP OUT
1629 901 12537
2624 981 18506
3626 573 9085
4631 2250 42534
5627 1610 20808
Signed-off-by: Luiz
semantics.
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
drivers/virtio/virtio_balloon.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/virtio/virtio_balloon.c b/drivers/virtio/virtio_balloon.c
index bd3ae32..9d5fe2b 100644
--- a/drivers/virtio
On Sat, 12 Jan 2013 02:13:17 +0530
Amit Shah wrote:
> On (Tue) 18 Dec 2012 [18:17:30], Luiz Capitulino wrote:
> > The auto-ballooning feature automatically performs balloon inflate or
> > deflate based on host and guest memory pressure. This can help to
> > avoid swapping o
On Sat, 12 Jan 2013 02:13:17 +0530
Amit Shah amit.s...@redhat.com wrote:
On (Tue) 18 Dec 2012 [18:17:30], Luiz Capitulino wrote:
The auto-ballooning feature automatically performs balloon inflate or
deflate based on host and guest memory pressure. This can help to
avoid swapping or worse
On Fri, 4 Jan 2013 00:27:52 -0800
Anton Vorontsov wrote:
> - I've split the pach into two: 'shrinker' and 'levels' parts. While the
> full-fledged userland shrinker is an interesting idea, we don't have any
> users ready for it, so I won't advocate for it too much.
For the next version of
On Fri, 4 Jan 2013 00:27:52 -0800
Anton Vorontsov anton.voront...@linaro.org wrote:
- I've split the pach into two: 'shrinker' and 'levels' parts. While the
full-fledged userland shrinker is an interesting idea, we don't have any
users ready for it, so I won't advocate for it too much.
On Thu, 20 Dec 2012 05:24:12 +
Dietmar Maurer wrote:
> > > Wow, you're fast! And I'm glad that it works for you, so we have two
> > > full-featured mempressure cgroup users already.
> >
> > Thanks, although I think we need more testing to be sure this does what we
> > want. I mean, the
On Thu, 20 Dec 2012 05:24:12 +
Dietmar Maurer diet...@proxmox.com wrote:
Wow, you're fast! And I'm glad that it works for you, so we have two
full-featured mempressure cgroup users already.
Thanks, although I think we need more testing to be sure this does what we
want. I mean,
On Wed, 19 Dec 2012 09:55:58 -0200
Rafael Aquini wrote:
> On Tue, Dec 18, 2012 at 06:17:29PM -0200, Luiz Capitulino wrote:
> > Today, the balloon_lock mutex is taken and released by fill_balloon()
> > and leak_balloon() when both functions are entered and when
On Tue, 18 Dec 2012 14:53:30 -0800
Anton Vorontsov wrote:
> Hello Luiz,
>
> On Tue, Dec 18, 2012 at 06:16:55PM -0200, Luiz Capitulino wrote:
> > The auto-ballooning feature automatically performs balloon inflate
> > or deflate based on host and guest memory pressure. This
On Tue, 18 Dec 2012 14:53:30 -0800
Anton Vorontsov anton.voront...@linaro.org wrote:
Hello Luiz,
On Tue, Dec 18, 2012 at 06:16:55PM -0200, Luiz Capitulino wrote:
The auto-ballooning feature automatically performs balloon inflate
or deflate based on host and guest memory pressure. This can
On Wed, 19 Dec 2012 09:55:58 -0200
Rafael Aquini aqu...@redhat.com wrote:
On Tue, Dec 18, 2012 at 06:17:29PM -0200, Luiz Capitulino wrote:
Today, the balloon_lock mutex is taken and released by fill_balloon()
and leak_balloon() when both functions are entered and when they
return
kernel seems to spin when the host is performing a long
auto-inflate
Signed-off-by: Luiz Capitulino
---
drivers/virtio/virtio_balloon.c | 54 +
include/uapi/linux/virtio_balloon.h | 1 +
2 files changed, 55 insertions(+)
diff --git a/drivers/virtio
(please, never mind the repo name):
git://repo.or.cz/qemu/qmp-unstable.git balloon/auto-ballooning/rfc
Any feedback is appreciated!
Luiz Capitulino (2):
virtio_balloon: move locking to the balloon thread
virtio_balloon: add auto-ballooning support
drivers/virtio/virtio_balloon.c | 60
.
The reason for this move is that the next commit will introduce
a shrinker callback for the balloon driver, which will also call
leak_balloon() but will require different locking semantics.
Signed-off-by: Luiz Capitulino
---
drivers/virtio/virtio_balloon.c | 6 ++
1 file changed, 2 insertions
.
The reason for this move is that the next commit will introduce
a shrinker callback for the balloon driver, which will also call
leak_balloon() but will require different locking semantics.
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
drivers/virtio/virtio_balloon.c | 6 ++
1 file
(please, never mind the repo name):
git://repo.or.cz/qemu/qmp-unstable.git balloon/auto-ballooning/rfc
Any feedback is appreciated!
Luiz Capitulino (2):
virtio_balloon: move locking to the balloon thread
virtio_balloon: add auto-ballooning support
drivers/virtio/virtio_balloon.c | 60
kernel seems to spin when the host is performing a long
auto-inflate
Signed-off-by: Luiz Capitulino lcapitul...@redhat.com
---
drivers/virtio/virtio_balloon.c | 54 +
include/uapi/linux/virtio_balloon.h | 1 +
2 files changed, 55 insertions(+)
diff --git
On Wed, 28 Nov 2012 17:27:51 -0800
Anton Vorontsov wrote:
> On Wed, Nov 28, 2012 at 03:14:32PM -0800, Andrew Morton wrote:
> [...]
> > Compare this with the shrink_slab() shrinkers. With these, the VM can
> > query and then control the clients. If something goes wrong or is out
> > of balance,
On Wed, 28 Nov 2012 17:27:51 -0800
Anton Vorontsov anton.voront...@linaro.org wrote:
On Wed, Nov 28, 2012 at 03:14:32PM -0800, Andrew Morton wrote:
[...]
Compare this with the shrink_slab() shrinkers. With these, the VM can
query and then control the clients. If something goes wrong or is
Hi Anton,
On Wed, 7 Nov 2012 02:53:49 -0800
Anton Vorontsov wrote:
> Hi all,
>
> This is the third RFC. As suggested by Minchan Kim, the API is much
> simplified now (comparing to vmevent_fd):
Which tree is this against? I'd like to try this series, but it doesn't
apply to Linus tree.
--
To
Hi Anton,
On Wed, 7 Nov 2012 02:53:49 -0800
Anton Vorontsov anton.voront...@linaro.org wrote:
Hi all,
This is the third RFC. As suggested by Minchan Kim, the API is much
simplified now (comparing to vmevent_fd):
Which tree is this against? I'd like to try this series, but it doesn't
apply
On Wed, 29 Aug 2012 13:18:54 +0800
Wen Congyang wrote:
> We can know the guest is panicked when the guest runs on xen.
> But we do not have such feature on kvm.
What's the status of this series?
It got lost in my queue and I ended up not reviewing it, but it seems
to be stuck.
>
> Another
On Wed, 29 Aug 2012 13:18:54 +0800
Wen Congyang we...@cn.fujitsu.com wrote:
We can know the guest is panicked when the guest runs on xen.
But we do not have such feature on kvm.
What's the status of this series?
It got lost in my queue and I ended up not reviewing it, but it seems
to be
501 - 588 of 588 matches
Mail list logo
