From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Dan Williams <dcbw@redhat.com>
Cc: davem@davemloft.net, kuba@kernel.org, bjorn.andersson@linaro.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] Migrate QRTR Nameservice to Kernel
Date: Thu, 13 Feb 2020 21:00:08 +0530 [thread overview]
Message-ID: <20200213153007.GA26254@mani> (raw)
In-Reply-To: <34daecbeb05d31e30ef11574f873553290c29d16.camel@redhat.com>
Hi Dan,
On Thu, Feb 13, 2020 at 09:22:39AM -0600, Dan Williams wrote:
> On Thu, 2020-02-13 at 14:44 +0530, Manivannan Sadhasivam wrote:
> > Hello,
> >
> > This patchset migrates the Qualcomm IPC Router (QRTR) Nameservice
> > from userspace
> > to kernel under net/qrtr.
> >
> > The userspace implementation of it can be found here:
> > https://github.com/andersson/qrtr/blob/master/src/ns.c
> >
> > This change is required for enabling the WiFi functionality of some
> > Qualcomm
> > WLAN devices using ATH11K without any dependency on a userspace
> > daemon.
>
> Just out of curiousity, what's the motivation for not requiring a
> userspace daemon? What are the downsides of the current userspace
> daemon implementation?
>
The primary motivation is to eliminate the need for installing and starting
a userspace tool for the basic WiFi usage. This will be critical for the
Qualcomm WLAN devices deployed in x86 laptops.
Also, there are some plans to implement QRTR link negotiation based on this
in future.
Thanks,
Mani
> Dan
>
> > The original userspace code is published under BSD3 license. For
> > migrating it
> > to Linux kernel, I have adapted Dual BSD/GPL license.
> >
> > This patchset has been verified on Dragonboard410c and Intel NUC with
> > QCA6390
> > WLAN device.
> >
> > Thanks,
> > Mani
> >
> > Manivannan Sadhasivam (2):
> > net: qrtr: Migrate nameservice to kernel from userspace
> > net: qrtr: Fix the local node ID as 1
> >
> > net/qrtr/Makefile | 2 +-
> > net/qrtr/ns.c | 730
> > ++++++++++++++++++++++++++++++++++++++++++++++
> > net/qrtr/qrtr.c | 51 +---
> > net/qrtr/qrtr.h | 4 +
> > 4 files changed, 746 insertions(+), 41 deletions(-)
> > create mode 100644 net/qrtr/ns.c
> >
>
next prev parent reply other threads:[~2020-02-13 15:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-13 9:14 [PATCH 0/2] Migrate QRTR Nameservice to Kernel Manivannan Sadhasivam
2020-02-13 9:14 ` [PATCH 1/2] net: qrtr: Migrate nameservice to kernel from userspace Manivannan Sadhasivam
2020-02-17 2:56 ` David Miller
2020-06-16 18:48 ` Qais Yousef
2020-06-19 14:46 ` Manivannan Sadhasivam
2020-06-19 15:03 ` Qais Yousef
2020-02-13 9:14 ` [PATCH 2/2] net: qrtr: Fix the local node ID as 1 Manivannan Sadhasivam
2020-02-13 15:22 ` [PATCH 0/2] Migrate QRTR Nameservice to Kernel Dan Williams
2020-02-13 15:30 ` Manivannan Sadhasivam [this message]
2020-02-13 15:47 ` David Miller
2020-02-14 7:08 ` Manivannan Sadhasivam
2020-02-14 9:11 ` Manivannan Sadhasivam
2020-02-16 15:52 ` Kalle Valo
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=20200213153007.GA26254@mani \
--to=manivannan.sadhasivam@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=dcbw@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@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).