From: Karthikeyan Ramasubramanian <kramasub@codeaurora.org>
To: David Miller <davem@davemloft.net>
Cc: 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 11:06:18 -0600 [thread overview]
Message-ID: <4DF0FD8A.1000304@codeaurora.org> (raw)
In-Reply-To: <20110609.001149.2112721409565728649.davem@davemloft.net>
On 6/9/2011 1:11 AM, David Miller wrote:
>
> There is no reason to create a whole new socket address family, use
> genetlink instead.
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
The prospect of using NETLINK sockets was investigated and it seems to
be supporting the communication between user-space and kernel-space
processes.
One of the requirements/goals for this MSM_IPC Router is to enable the
communication between the processes running on different processors &
OSes, and the addressing mechanism of NETLINK sockets is insufficient to
address the processes running in different processors and OSes.
We also have the requirements of built-in name service, remote process's
status detection, location transparency etc. That is the reason for this
home-grown solution with a requirement for new socket address family.
Please let me know if you need any other information.
Thanks and Regards,
Karthik.
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.
next prev parent reply other threads:[~2011-06-09 17:06 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 [this message]
2011-06-09 19:35 ` David Miller
2011-06-09 20:15 ` Arnd Bergmann
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=4DF0FD8A.1000304@codeaurora.org \
--to=kramasub@codeaurora.org \
--cc=davem@davemloft.net \
--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).