From: Olaf Hering <olaf@aepfle.de>
To: Keir Fraser <keir.xen@gmail.com>
Cc: xen-devel@lists.xensource.com,
Andres Lagar-Cavilla <andres@lagarcavilla.org>,
adin@gridncetric.ca
Subject: Re: RFC: mem_event: use wait queue when ring is full
Date: Wed, 23 Nov 2011 19:23:57 +0100 [thread overview]
Message-ID: <20111123182357.GB26648@aepfle.de> (raw)
In-Reply-To: <CAF2DB24.256F1%keir.xen@gmail.com>
On Wed, Nov 23, Keir Fraser wrote:
> On 23/11/2011 16:49, "Olaf Hering" <olaf@aepfle.de> wrote:
> > I'm not proposing to include my patch as is, because it has one issue:
> > wake_up will start all waiting vcpus even if there is just a single slot
> > free in the ringbuffer. You patch is better in this respect because only
> > a few will be started again.
>
> Do you need a wake_up_one() function?
I'm not sure.
In case of paging, if gfn 1234 is missing, several vcpus may wait for it
to come back. Other vcpus may wait for other gfns. So if we had a struct
waitqueue_head for gfn 1234, and other individual gfns, that would help
for this case.
Since there cant be more gfns to wait for than the available guest
vcpus, a list of waitqueue_head's with a gfn attached to it would work.
If that sounds to crazy, or if I'm on the wrong track, how would you do that?
(Perhaps I should prepare a patch to demonstrate what I mean.)
Olaf
prev parent reply other threads:[~2011-11-23 18:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1126.1321998852.12970.xen-devel@lists.xensource.com>
2011-11-23 4:52 ` [PATCH 3 of 3] RFC: xenpaging: use waitqueue in ept_get Andres Lagar-Cavilla
2011-11-23 16:37 ` Olaf Hering
2011-11-23 17:36 ` Andres Lagar-Cavilla
2011-11-23 4:58 ` RFC: mem_event: use wait queue when ring is full Andres Lagar-Cavilla
2011-11-23 16:49 ` Olaf Hering
2011-11-23 17:17 ` Keir Fraser
2011-11-23 18:23 ` Olaf Hering [this message]
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=20111123182357.GB26648@aepfle.de \
--to=olaf@aepfle.de \
--cc=adin@gridncetric.ca \
--cc=andres@lagarcavilla.org \
--cc=keir.xen@gmail.com \
--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.