From: Olaf Hering <olaf@aepfle.de>
To: Andres Lagar-Cavilla <andres@lagarcavilla.org>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH 2 of 4] xenpaging: use wait queues
Date: Fri, 2 Dec 2011 18:34:12 +0100 [thread overview]
Message-ID: <20111202173411.GA30126@aepfle.de> (raw)
In-Reply-To: <188ac55da1f6e5f257ae01204118281c.squirrel@webmail.lagarcavilla.org>
On Fri, Dec 02, Andres Lagar-Cavilla wrote:
> A pager could nominate gfn's in batches, write them out in batches, evict
> them in batches. It's a bit of a longshot, but exemplifies the kinds of
> problems we need to think about when tinkering with the paging ABI.
I want to do something like that, using a separate ring instead of
individual domctls. However, its more an optimization than a bugfix so
its not a top priority for me. I see you already submitted changes to
simplify event channel handling.
> On that topic. Is there a reason why a page cannot be proactively paged in
> without attempting to map it first? I.e. move from p2m_ram_paging_out
> straight into p2m_ram_paging_in with paging_prep/_load? It would eliminate
> xenpaging's use of a page-in thread...
Maybe there are different ways to do that. The way ring buffers are
implemented now its not possible to send one-way events with the ring.
Olaf
next prev parent reply other threads:[~2011-12-02 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3014.1322742146.12970.xen-devel@lists.xensource.com>
2011-12-01 15:17 ` [PATCH 2 of 4] xenpaging: use wait queues Andres Lagar-Cavilla
2011-12-01 18:46 ` Olaf Hering
2011-12-01 20:02 ` Andres Lagar-Cavilla
2011-12-02 16:30 ` Andres Lagar-Cavilla
2011-12-02 16:43 ` Olaf Hering
2011-12-02 17:23 ` Andres Lagar-Cavilla
2011-12-02 17:34 ` Olaf Hering [this message]
2011-12-01 11:09 [PATCH 0 of 4] RFC: wait queue usage Olaf Hering
2011-12-01 11:09 ` [PATCH 2 of 4] xenpaging: use wait queues Olaf Hering
2011-12-15 12:28 ` Tim Deegan
2011-12-15 12:40 ` Olaf Hering
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=20111202173411.GA30126@aepfle.de \
--to=olaf@aepfle.de \
--cc=andres@lagarcavilla.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.