Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
From:   =?UTF-8?q?Micha=C5=82=20Lowas-Rzechonek?= 
        <michal.lowas-rzechonek@silvair.com>
To:     linux-bluetooth@vger.kernel.org
Subject: [RFC BlueZ 0/2] mesh: Deliver mesh packets over datagram socket
Date:   Tue, 16 Jun 2020 14:27:43 +0200
Message-Id: <20200616122745.25056-1-michal.lowas-rzechonek@silvair.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Sender: linux-bluetooth-owner@vger.kernel.org
Precedence: bulk

This patchset adds another D-Bus API for attaching applications, called
AttachFD.

When application uses that API, it receives one end of a datagram socket
pair, which it's supposed to recv() from in order to receive mesh
packets, instead of wating for *MessageReceived() calls over D-Bus.

This significantly reduces system load for high traffic environment
(e.g. an application that subscribes to a large number of publications
in a big network).

Message delivery is one way only: application is still supposed to call
*Send methods via D-Bus, although the socket pair is bidirectional, so
it would be possible to add sending as well.

Michał Lowas-Rzechonek (1):
  mesh: Implement AttachFD method

Przemysław Fierek (1):
  mesh: Add documentation for AttachFD

 doc/mesh-api.txt |  40 +++++++++++++++
 mesh/mesh.c      |  12 ++++-
 mesh/model.c     | 126 ++++++++++++++++++++++++++++++++++++++++++++++-
 mesh/node.c      |  83 ++++++++++++++++++++++++++++++-
 mesh/node.h      |   4 +-
 5 files changed, 259 insertions(+), 6 deletions(-)

-- 
2.20.1