From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: xen-devel@lists.xensource.com
Subject: Re: [RFC] PVFB: Add refresh period to XenStore parameters?
Date: Mon, 3 Mar 2008 11:07:15 +0000 [thread overview]
Message-ID: <20080303110715.GA4792@implementation.uk.xensource.com> (raw)
In-Reply-To: <20080229120806.GA8268@implementation.uk.xensource.com>
Hello,
There was no comment on my proposition below, should I consider that it
means people are fine with it? :)
Samuel
Samuel Thibault, le Fri 29 Feb 2008 12:08:07 +0000, a écrit :
> Sometimes the backend of PVFB knows that it doesn't need permanent
> refresh, when the window is minimized for instance (no refresh at all),
> or the administration tools know that the window is thumnailed, and so a
> slow refresh rate is fine. Also, some users may want to tune the
> refresh rate according to the smoothness they would like, balanced with
> the CPU time that requires.
>
> I've played with that idea a bit and it seems to work fine, saving
> computations and communications. I'm now wondering about the interface:
> it looks to me like it could be as simple as a "refresh-period" node in
> the backend part of XenStore: the front-end would watch it, and update
> the timing of its internal refresh loop, xenfb_fps in the case of Linux'
> xenfb for instance. A period of 0 would mean that no refresh is needed
> (e.g. minimized window)
next prev parent reply other threads:[~2008-03-03 11:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 12:08 [RFC] PVFB: Add refresh period to XenStore parameters? Samuel Thibault
2008-03-03 11:07 ` Samuel Thibault [this message]
2008-03-03 18:03 ` Markus Armbruster
2008-03-03 19:18 ` Samuel Thibault
2008-03-04 12:36 ` Trolle Selander
2008-03-04 14:32 ` Markus Armbruster
2008-03-04 14:49 ` Samuel Thibault
2008-03-04 15:11 ` Samuel Thibault
2008-03-04 15:48 ` Markus Armbruster
2008-03-04 16:12 ` Samuel Thibault
2008-03-04 17:06 ` Markus Armbruster
2008-03-04 17:19 ` Samuel Thibault
2008-03-05 8:03 ` Markus Armbruster
2008-03-05 9:59 ` Samuel Thibault
2008-05-01 17:55 ` Samuel Thibault
2008-05-02 16:06 ` Samuel Thibault
2008-05-05 8:26 ` Markus Armbruster
2008-05-05 9:18 ` Samuel Thibault
2008-05-05 9:58 ` Markus Armbruster
2008-05-05 10:21 ` Samuel Thibault
2008-05-05 16:50 ` Samuel Thibault
2008-05-06 13:50 ` Markus Armbruster
2008-05-06 14:07 ` Keir Fraser
2008-05-06 16:32 ` Samuel Thibault
2008-05-06 16:50 ` Markus Armbruster
2008-05-06 17:29 ` Samuel Thibault
2008-05-07 14:43 ` Markus Armbruster
2008-05-07 14:54 ` Samuel Thibault
2008-05-08 8:25 ` Markus Armbruster
2008-05-08 15:01 ` Samuel Thibault
2008-05-09 8:43 ` Markus Armbruster
2008-05-09 10:31 ` Samuel Thibault
2008-05-09 10:48 ` Markus Armbruster
2008-05-09 13:43 ` Samuel Thibault
2008-03-05 11:19 ` Markus Armbruster
2008-03-05 11:27 ` Samuel Thibault
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=20080303110715.GA4792@implementation.uk.xensource.com \
--to=samuel.thibault@eu.citrix.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.