From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: "David S. Miller" <davem@davemloft.net>,
Arun Kumar Neelakantam <aneela@codeaurora.org>,
Chris Lew <clew@codeaurora.org>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: [PATCH 0/5] QRTR flow control improvements
Date: Tue, 7 May 2019 23:06:38 -0700 [thread overview]
Message-ID: <20190508060643.30936-1-bjorn.andersson@linaro.org> (raw)
In order to prevent overconsumption of resources on the remote side QRTR
implements a flow control mechanism.
Move the handling of the incoming confirm_rx to the receiving process to ensure
incoming flow is controlled. Then implement outgoing flow control, using the
recommended algorithm of counting outstanding non-confirmed messages and
blocking when hitting a limit. The last three patches refactors the node
assignment and port lookup, in order to remove the worker in the receive path.
Bjorn Andersson (5):
net: qrtr: Move resume-tx transmission to recvmsg
net: qrtr: Implement outgoing flow control
net: qrtr: Migrate node lookup tree to spinlock
net: qrtr: Make qrtr_port_lookup() use RCU
net: qrtr: Remove receive worker
net/qrtr/qrtr.c | 265 +++++++++++++++++++++++++++++++++++-------------
1 file changed, 196 insertions(+), 69 deletions(-)
--
2.18.0
next reply other threads:[~2019-05-08 6:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-08 6:06 Bjorn Andersson [this message]
2019-05-08 6:06 ` [PATCH 1/5] net: qrtr: Move resume-tx transmission to recvmsg Bjorn Andersson
2019-05-09 10:23 ` Arun Kumar Neelakantam
2019-05-08 6:06 ` [PATCH 2/5] net: qrtr: Implement outgoing flow control Bjorn Andersson
2019-05-08 16:41 ` David Miller
2019-05-13 21:26 ` Chris Lew
2019-05-08 6:06 ` [PATCH 3/5] net: qrtr: Migrate node lookup tree to spinlock Bjorn Andersson
2019-05-08 6:06 ` [PATCH 4/5] net: qrtr: Make qrtr_port_lookup() use RCU Bjorn Andersson
2019-05-08 6:06 ` [PATCH 5/5] net: qrtr: Remove receive worker Bjorn Andersson
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=20190508060643.30936-1-bjorn.andersson@linaro.org \
--to=bjorn.andersson@linaro.org \
--cc=aneela@codeaurora.org \
--cc=clew@codeaurora.org \
--cc=davem@davemloft.net \
--cc=linux-arm-msm@vger.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).