From: Olaf Hering <olaf@aepfle.de>
To: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Cc: xen-devel@lists.xensource.com, ian.campbell@citrix.com,
andres@gridcentric.ca, tim@xen.org, keir.xen@gmail.com,
jbeulich@suse.com, ian.jackson@citrix.com, adin@gridcentric.ca
Subject: Re: [PATCH 2 of 5] Improve ring management for memory events. Do not lose guest events
Date: Mon, 5 Dec 2011 12:23:59 +0100 [thread overview]
Message-ID: <20111205112358.GB28908@aepfle.de> (raw)
In-Reply-To: <457bf805a9709501746d2073fcd9082d.squirrel@webmail.lagarcavilla.org>
On Thu, Dec 01, Andres Lagar-Cavilla wrote:
> MAX_HVM_VCPUS sits at 128 right now. Haven't compile checked, but that
> probably means we would need a two page ring. And then, when 1024-cpu
> hosts arrive and we grow MAX_HVM_VCPUS, we grow the ring size again.
The ring has 64 entries.
> Or, we could limit the constraint to the number of online vcpus, which
> would get somewhat tricky for vcpu hot-plugging.
>
> I can fix that separately, once there is a decision on which way to go re
> ring management.
I just sent "[PATCH] mem_event: use wait queue when ring is full" to the
list. This version ought to work, it takes the request from both target
and foreign cpus into account and leaves at lease one slot for the
target.
Olaf
next prev parent reply other threads:[~2011-12-05 11:23 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-29 21:55 [PATCH 0 of 5] Memory event interface improvements Andres Lagar-Cavilla
2011-11-29 21:55 ` [PATCH 1 of 5] Allow decrease_reservation to be preempted if remove_page returns negative Andres Lagar-Cavilla
2011-11-29 21:55 ` [PATCH 2 of 5] Improve ring management for memory events. Do not lose guest events Andres Lagar-Cavilla
2011-11-30 12:58 ` Olaf Hering
2011-11-30 15:11 ` Andres Lagar-Cavilla
2011-12-01 15:36 ` Olaf Hering
2011-12-01 14:51 ` Olaf Hering
2011-12-01 15:25 ` Andres Lagar-Cavilla
2011-12-05 11:23 ` Olaf Hering [this message]
2011-12-05 15:27 ` Andres Lagar-Cavilla
2011-12-01 18:10 ` Tim Deegan
2011-12-01 10:19 ` Keir Fraser
2011-12-01 18:27 ` Andres Lagar-Cavilla
2011-12-01 18:23 ` Andres Lagar-Cavilla
2011-11-29 21:55 ` [PATCH 3 of 5] Create a generic callback mechanism for Xen-bound event channels Andres Lagar-Cavilla
2011-11-29 21:55 ` [PATCH 4 of 5] Make the prototype of p2m_mem_access_resume consistent Andres Lagar-Cavilla
2011-12-01 18:01 ` Tim Deegan
2011-12-01 18:05 ` Andres Lagar-Cavilla
2011-11-29 21:55 ` [PATCH 5 of 5] Allow memevent responses to be signaled via the event channel Andres Lagar-Cavilla
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20111205112358.GB28908@aepfle.de \
--to=olaf@aepfle.de \
--cc=adin@gridcentric.ca \
--cc=andres@gridcentric.ca \
--cc=andres@lagarcavilla.org \
--cc=ian.campbell@citrix.com \
--cc=ian.jackson@citrix.com \
--cc=jbeulich@suse.com \
--cc=keir.xen@gmail.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.