linux-kernel - Re: [PATCH v4 0/5] QRTR flow control improvements

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <20200114.183748.275989716164464774.davem@davemloft.net>
Date:   Tue, 14 Jan 2020 18:37:48 -0800 (PST)
From:   David Miller <davem@...emloft.net>
To:     bjorn.andersson@...aro.org
Cc:     aneela@...eaurora.org, clew@...eaurora.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org
Subject: Re: [PATCH v4 0/5] QRTR flow control improvements

From: Bjorn Andersson <bjorn.andersson@...aro.org>
Date: Mon, 13 Jan 2020 23:56:58 -0800

> 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.

Series applied to net-next, thank you.