From: Anthony Liguori <aliguori@us.ibm.com>
To: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>, xen-devel@lists.xensource.com
Subject: vram_dirty vs. shadow paging dirty tracking
Date: Tue, 13 Mar 2007 14:32:56 -0500 [thread overview]
Message-ID: <45F6FC68.3040207@us.ibm.com> (raw)
When thinking about multithreading the device model, it occurred to me
that it's a little odd that we're doing a memcmp to determine which
portions of the VRAM has changed. Couldn't we just use dirty page
tracking in the shadow paging code? That should significantly lower the
overhead of this plus I believe the infrastructure is already mostly
there in the shadow2 code.
Is this a sane idea?
Regards,
Anthony Liguori
next reply other threads:[~2007-03-13 19:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 19:32 Anthony Liguori [this message]
2007-03-13 21:02 ` vram_dirty vs. shadow paging dirty tracking Ian Pratt
2007-03-13 21:30 ` Anthony Liguori
2007-03-14 0:17 ` Ian Pratt
2007-03-14 8:22 ` Zhai, Edwin
2007-03-14 16:00 ` Anthony Liguori
2007-03-15 2:59 ` Zhai, Edwin
2007-03-15 3:22 ` Dong, Eddie
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=45F6FC68.3040207@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--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.