All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nivedita Singhvi <niv@us.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Lon Hohberger <lhh@redhat.com>, xen-devel@lists.xensource.com
Subject: Re: RFC: "local" communications
Date: Wed, 15 Jun 2005 15:07:14 -0700	[thread overview]
Message-ID: <42B0A692.6000306@us.ibm.com> (raw)
In-Reply-To: <42B0A3CD.60505@us.ibm.com>

Anthony Liguori wrote:
> Nivedita Singhvi wrote:
> 
>> UDP or raw sockets will be somewhat better, although AF_UNIX
>> would be best of all (albeit with its own constraints).
> 
> 
> I was thinking of a raw interface although a UDP-like protocol would be 
> kind of neat (so that you could do multiplexing).

It would be less work and easier on the apps to use UDP than raw,
but that's just my experience (and, potentially more bugs). This
could be solved by having a user space library wrap the details
and call a simple low level protocol over raw sockets.

>> Which datagram service, Anthony?  Having a small lib like this
>> would be a good idea, although the benefit would be in the details,
>> and of course, depending on how many apps we need to support that
>> we don't want to modify...
> 
> 
> I must admit I've not put much thought into it.  What are your thoughts?

Me neither, much, yet, :). But, it would be nice to make things easy
for the large number of apps which need intra-node communication. At
the moment, they fall into the two categories of strictly intra-node
versus common-over-intra_off_node. Much easier designing things for
the former.

thanks,
Nivedita

  reply	other threads:[~2005-06-15 22:07 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-15 20:08 RFC: "local" communications Rik van Riel
2005-06-15 20:24 ` Anthony Liguori
2005-06-15 21:31   ` Nivedita Singhvi
2005-06-15 21:55     ` Anthony Liguori
2005-06-15 22:07       ` Nivedita Singhvi [this message]
2005-06-16 16:15     ` Lon Hohberger
2005-06-16  2:44   ` Rusty Russell
  -- strict thread matches above, loose matches on Subject: below --
2005-06-15 21:53 Ian Pratt
2005-06-15 22:10 ` Nivedita Singhvi
2005-06-15 22:43 ` Rik van Riel
2005-06-16 16:19   ` Lon Hohberger
2005-06-15 22:32 Ian Pratt
2005-06-16  2:59 ` Rusty Russell

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=42B0A692.6000306@us.ibm.com \
    --to=niv@us.ibm.com \
    --cc=aliguori@us.ibm.com \
    --cc=lhh@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.