All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@eu.citrix.com>
To: Markus Armbruster <armbru@redhat.com>, xen-devel@lists.xensource.com
Subject: Re: [RFC] PVFB: Add refresh period to XenStore parameters?
Date: Tue, 4 Mar 2008 15:11:40 +0000	[thread overview]
Message-ID: <20080304151140.GB9230@implementation.uk.xensource.com> (raw)
In-Reply-To: <20080304144952.GA9230@implementation.uk.xensource.com>

Samuel Thibault, le Tue 04 Mar 2008 14:49:52 +0000, a écrit :
> Markus Armbruster, le Tue 04 Mar 2008 15:32:57 +0100, a écrit :
> > Depends on who does the tinkering.  If its the backend, then nothing
> > is easier than sending a message through the ring.
> > 
> > On the other hand, if this is just a hack to make a particular
> > frontend less inefficient, then using XenStore at least keeps it out
> > of the PVFB protocol.
> 
> But the backend still needs to notify the frontend when it should switch
> modes.  Another way to go would be to only add to the PVFB protocol some
> "expose on/off" events, and let the front-end decide of the rate to
> adopt.

Mmm, that said, the backend remains the most close for the user to
select the refresh rate.

Samuel

  reply	other threads:[~2008-03-04 15:11 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
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 [this message]
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=20080304151140.GB9230@implementation.uk.xensource.com \
    --to=samuel.thibault@eu.citrix.com \
    --cc=armbru@redhat.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.