From: Rusty Russell <rusty@rustcorp.com.au>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel List <xen-devel@lists.xensource.com>,
Christian Limpach <Christian.Limpach@cl.cam.ac.uk>
Subject: Re: /proc/xen/xenbus supports watch?
Date: Fri, 23 Sep 2005 08:54:48 +1000 [thread overview]
Message-ID: <1127429689.2722.2.camel@localhost.localdomain> (raw)
In-Reply-To: <b5423e9d922e98b290db80ff4d0cba9c@cl.cam.ac.uk>
On Thu, 2005-09-22 at 10:36 +0100, Keir Fraser wrote:
> On 22 Sep 2005, at 03:07, Rusty Russell wrote:
>
> > Exactly! So you would have me implement multiplexing code in the
> > kernel, demultiplexing code in the daemon, checking code in the kernel
> > to make sure we don't corrupt the shared comms channel, for no reason.
>
> Better to implement simple mux/demux code than pain-in-the-arse
> save/restore code.
But but but... it doesn't *help*. That's the entire point!
OK, please describe, in simple terms, why you think save/restore is
different if we multiplex across a single transport?
Rusty.
--
A bad analogy is like a leaky screwdriver -- Richard Braakman
next prev parent reply other threads:[~2005-09-22 22:54 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-08 8:02 /proc/xen/xenbus supports watch? NAHieu
2005-09-08 10:38 ` Christian Limpach
2005-09-09 0:43 ` Rusty Russell
2005-09-13 9:42 ` Christian Limpach
2005-09-14 0:21 ` Rusty Russell
2005-09-14 8:24 ` Christian Limpach
2005-09-14 9:18 ` Rusty Russell
2005-09-14 12:55 ` Christian Limpach
2005-09-15 1:39 ` Rusty Russell
2005-09-15 10:53 ` Keir Fraser
2005-09-17 8:26 ` Rusty Russell
2005-09-17 8:33 ` Keir Fraser
2005-09-19 0:11 ` Rusty Russell
2005-09-19 8:54 ` Keir Fraser
2005-09-20 11:01 ` Rusty Russell
2005-09-21 9:35 ` Keir Fraser
2005-09-22 2:07 ` Rusty Russell
2005-09-22 9:36 ` Keir Fraser
2005-09-22 22:54 ` Rusty Russell [this message]
2005-09-23 9:17 ` Keir Fraser
2005-09-25 3:29 ` Rusty Russell
2005-09-25 11:02 ` Keir Fraser
2005-09-25 11:33 ` Keir Fraser
2005-09-25 18:55 ` Christian Limpach
2005-09-26 6:36 ` Rusty Russell
2005-09-26 7:33 ` Keir Fraser
2005-09-26 18:51 ` Christian Limpach
2005-09-26 19:30 ` Keir Fraser
2005-09-27 6:48 ` Rusty Russell
2005-09-27 7:15 ` Rusty Russell
2005-09-27 23:31 ` David Hopwood
2005-09-25 23:06 ` Rusty Russell
2005-09-21 9:39 ` Keir Fraser
2005-09-21 11:42 ` harry
2005-09-22 2:22 ` Rusty Russell
2005-09-22 9:35 ` Keir Fraser
2005-09-22 23:51 ` Rusty Russell
2005-09-23 1:01 ` Andrew Warfield
2005-09-25 0:57 ` Rusty Russell
2005-09-25 11:09 ` Keir Fraser
2005-09-25 22:52 ` Rusty Russell
2005-09-23 9:24 ` Keir Fraser
2005-09-25 1:09 ` Rusty Russell
2005-09-17 17:40 ` Christian Limpach
2005-09-19 0:19 ` Rusty Russell
2005-09-15 11:02 ` Christian Limpach
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=1127429689.2722.2.camel@localhost.localdomain \
--to=rusty@rustcorp.com.au \
--cc=Christian.Limpach@cl.cam.ac.uk \
--cc=Keir.Fraser@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.