From: Arnd Bergmann <arnd@arndb.de>
To: David Miller <davem@davemloft.net>
Cc: 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, 9 Jun 2011 22:15:49 +0200 [thread overview]
Message-ID: <201106092215.49079.arnd@arndb.de> (raw)
In-Reply-To: <20110609.123553.784125057506332397.davem@davemloft.net>
On Thursday 09 June 2011 21:35:53 David Miller wrote:
> From: Karthikeyan Ramasubramanian <kramasub@codeaurora.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
next prev parent reply other threads:[~2011-06-09 20:15 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 [this message]
2011-06-09 20:41 ` Bryan Huntsman
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=201106092215.49079.arnd@arndb.de \
--to=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 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.