From: Bryan Huntsman <bryanh@codeaurora.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: David Miller <davem@davemloft.net>,
kramasub@codeaurora.org, netdev@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 2/3] net: msm_ipc: Add user-space support for MSM_IPC Router
Date: Thu, 09 Jun 2011 13:41:53 -0700 [thread overview]
Message-ID: <4DF13011.6060003@codeaurora.org> (raw)
In-Reply-To: <201106092215.49079.arnd@arndb.de>
On 06/09/2011 01:15 PM, Arnd Bergmann wrote:
> I can see some good use cases for having a socket to do IPC between OS
> images that have a shared memory interconnect. What I see as most
> problematic is to have it defined in a way that is tightly connected
> to specific hardware from one vendor. If the protocol was defined
> in a way that is useful for communication between virtual machines
> (e.g. on top of virtio) and tranparent PCI bridges, it would probably
> be much more acceptable.
>
> Arnd
Yeah, we're trying to figure out the best way to do socket-based
communication between various images within a SoC. I was thinking that
some kind of registration scheme would be necessary for the new AF to
support different SoCs and communication mechanisms. We'll take a look
at ways to have a generic implementation. Thanks.
- Bryan
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
prev parent reply other threads:[~2011-06-09 20:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 17:51 [PATCH 2/3] net: msm_ipc: Add user-space support for MSM_IPC Router Karthikeyan Ramasubramanian
2011-06-09 7:11 ` David Miller
2011-06-09 17:06 ` Karthikeyan Ramasubramanian
2011-06-09 19:35 ` David Miller
2011-06-09 20:15 ` Arnd Bergmann
2011-06-09 20:41 ` Bryan Huntsman [this message]
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=4DF13011.6060003@codeaurora.org \
--to=bryanh@codeaurora.org \
--cc=arnd@arndb.de \
--cc=davem@davemloft.net \
--cc=kramasub@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).