[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200408.143327.2268546094613330028.davem@davemloft.net>
Date: Wed, 08 Apr 2020 14:33:27 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: wenhu.wang@...o.com
Cc: akpm@...ux-foundation.org, kuba@...nel.org,
gregkh@...uxfoundation.org, tglx@...utronix.de,
bjorn.andersson@...aro.org, hofrat@...dl.org, allison@...utok.net,
johannes.berg@...el.com, arnd@...db.de, cjhuang@...eaurora.org,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
kernel@...o.com
Subject: Re: [PATCH RESEND] net: qrtr: support qrtr service and lookup route
From: Wang Wenhu <wenhu.wang@...o.com>
Date: Wed, 8 Apr 2020 03:46:35 -0700
> QSR implements maintenance of qrtr services and lookups. It would
> be helpful for developers to work with QRTR without the none-opensource
> user-space implementation part of IPC Router.
>
> As we know, the extremely important point of IPC Router is the support
> of services form different nodes. But QRTR was pushed into mainline
> without route process support of services, and the router port process
> is implemented in user-space as none-opensource codes, which is an
> great unconvenience for developers.
>
> QSR also implements a interface via chardev and a set of sysfs class
> files for the communication and debugging in user-space. We can get
> service and lookup entries conveniently via sysfs file in /sys/class/qsr/.
> Currently add-server, del-server, add-lookup and del-lookup control
> packatets are processed and enhancements could be taken easily upon
> currently implementation.
>
> Signed-off-by: Wang Wenhu <wenhu.wang@...o.com>
New features are only appropriate for net-next which is closed right now.
Powered by blists - more mailing lists