LKML Archive on lore.kernel.org help / color / mirror / Atom feed
From: Bjorn Andersson <bjorn.andersson@linaro.org> To: "David S. Miller" <davem@davemloft.net> Cc: Arun Kumar Neelakantam <aneela@codeaurora.org>, Chris Lew <clew@codeaurora.org>, netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org Subject: [PATCH v2 0/5] QRTR flow control improvements Date: Thu, 30 May 2019 18:17:48 -0700 [thread overview] Message-ID: <20190531011753.11840-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 | 308 +++++++++++++++++++++++++++++++++++++----------- 1 file changed, 239 insertions(+), 69 deletions(-) -- 2.18.0
next reply other threads:[~2019-05-31 1:17 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-05-31 1:17 Bjorn Andersson [this message] 2019-05-31 1:17 ` [PATCH v2 1/5] net: qrtr: Move resume-tx transmission to recvmsg Bjorn Andersson 2019-05-31 1:17 ` [PATCH v2 2/5] net: qrtr: Implement outgoing flow control Bjorn Andersson 2019-05-31 21:46 ` David Miller 2019-05-31 1:17 ` [PATCH v2 3/5] net: qrtr: Migrate node lookup tree to spinlock Bjorn Andersson 2019-05-31 1:17 ` [PATCH v2 4/5] net: qrtr: Make qrtr_port_lookup() use RCU Bjorn Andersson 2019-05-31 1:17 ` [PATCH v2 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=20190531011753.11840-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: linkBe 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).