LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Chris Lew <clew@codeaurora.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>,
"David S. Miller" <davem@davemloft.net>
Cc: Arun Kumar Neelakantam <aneela@codeaurora.org>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3 2/5] net: qrtr: Implement outgoing flow control
Date: Thu, 9 Jan 2020 19:07:59 -0800 [thread overview]
Message-ID: <18c9b140-61d4-13b1-f10e-af3321dfca38@codeaurora.org> (raw)
In-Reply-To: <20200107054713.3909260-3-bjorn.andersson@linaro.org>
Hey Bjorn,
Some minor comments.
On 1/6/2020 9:47 PM, Bjorn Andersson wrote:
> +/**
> + * qrtr_tx_flow_failed() - flag that tx of confirm_rx flagged messages failed
> + * @node: qrtr_node that the packet is to be send to
> + * @dest_node: node id of the destination
> + * @dest_port: port number of the destination
> + *
> + * Signal that the transmission of a message with confirm_rx flag failed. The
> + * flow's "pending" counter will keep incrementing towards QRTR_TX_FLOW_HIGH,
> + * at which point transmission would stall forever waiting for the resume TX
> + * message associated with the dropped confirm_rx message.
> + * Work around this by marking the flow as having a failed transmission and
> + * cause the next transmission attempt to be sent with the confirm_rx.
> + */
> +static void qrtr_tx_flow_failed(struct qrtr_node *node, int dest_node,
> + int dest_port)
> +{
> + unsigned long key = (u64)dest_node << 32 | dest_port;
> + struct qrtr_tx_flow *flow;
> +
> + flow = radix_tree_lookup(&node->qrtr_tx_flow, key);
> + if (flow) {
> + spin_lock_irq(&flow->resume_tx.lock);
> + flow->tx_failed = 1;
> + spin_unlock_irq(&flow->resume_tx.lock);
> + }
Might be good to take qrtr_tx_lock when accessing the qrtr_tx_flow radix
tree here.
> @@ -408,6 +570,8 @@ int qrtr_endpoint_register(struct qrtr_endpoint *ep, unsigned int nid)
> node->nid = QRTR_EP_NID_AUTO;
> node->ep = ep;
>
> + INIT_RADIX_TREE(&node->qrtr_tx_flow, GFP_KERNEL);
> +
mutex_init(&node->qrtr_tx_lock);
> qrtr_node_assign(node, nid);
>
> mutex_lock(&qrtr_node_lock);
Thanks,
Chris
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2020-01-10 3:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 5:47 [PATCH v3 0/5] QRTR flow control improvements Bjorn Andersson
2020-01-07 5:47 ` [PATCH v3 1/5] net: qrtr: Move resume-tx transmission to recvmsg Bjorn Andersson
2020-01-07 5:47 ` [PATCH v3 2/5] net: qrtr: Implement outgoing flow control Bjorn Andersson
2020-01-07 21:16 ` David Miller
2020-01-10 3:07 ` Chris Lew [this message]
2020-01-07 5:47 ` [PATCH v3 3/5] net: qrtr: Migrate node lookup tree to spinlock Bjorn Andersson
2020-01-07 5:47 ` [PATCH v3 4/5] net: qrtr: Make qrtr_port_lookup() use RCU Bjorn Andersson
2020-01-07 5:47 ` [PATCH v3 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=18c9b140-61d4-13b1-f10e-af3321dfca38@codeaurora.org \
--to=clew@codeaurora.org \
--cc=aneela@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--subject='Re: [PATCH v3 2/5] net: qrtr: Implement outgoing flow control' \
/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
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).