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] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 9 Jun 2011 22:15:49 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	David Miller <davem@...emloft.net>
Cc:	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 Thursday 09 June 2011 21:35:53 David Miller wrote:
> From: Karthikeyan Ramasubramanian <kramasub@...eaurora.org>
> Date: Thu, 09 Jun 2011 11:06:18 -0600
> 
> > Please let me know if you need any other information.
> 
> I don't agree with creating all of this non-trivial infrastructure
> for what seems to be an obscure protocol stack.
> 
> You can do all of this in userspace, it seems.

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
--
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