netdev - Re: [PATCH 2/3] net: msm_ipc: Add user-space support for MSM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4DF13011.6060003@codeaurora.org>
Date:	Thu, 09 Jun 2011 13:41:53 -0700
From:	Bryan Huntsman <bryanh@...eaurora.org>
To:	Arnd Bergmann <arnd@...db.de>
CC:	David Miller <davem@...emloft.net>, kramasub@...eaurora.org,
	netdev@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH 2/3] net: msm_ipc: Add user-space support for MSM_IPC
 Router

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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html