From: Evan Green <evgreen@chromium.org>
To: Georgi Djakov <georgi.djakov@linaro.org>
Cc: linux-pm@vger.kernel.org, Sean Sweeney <seansw@qti.qualcomm.com>,
LKML <linux-kernel@vger.kernel.org>,
David Dai <daidavid1@codeaurora.org>,
Doug Anderson <dianders@chromium.org>,
amit.kucheria@linaro.org,
Bjorn Andersson <bjorn.andersson@linaro.org>,
linux-arm-msm <linux-arm-msm@vger.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v2 1/2] interconnect: Add support for path tags
Date: Thu, 11 Jul 2019 10:06:04 -0700 [thread overview]
Message-ID: <CAE=gft6=5txOBNEyrzqPEgaZc8ehd4sm5CmDBYOaV+o3-vCNWw@mail.gmail.com> (raw)
In-Reply-To: <20190618091724.28232-2-georgi.djakov@linaro.org>
Hi Georgi and David,
On Tue, Jun 18, 2019 at 2:17 AM Georgi Djakov <georgi.djakov@linaro.org> wrote:
>
> Consumers may have use cases with different bandwidth requirements based
> on the system or driver state. The consumer driver can append a specific
> tag to the path and pass this information to the interconnect platform
> driver to do the aggregation based on this state.
>
> Introduce icc_set_tag() function that will allow the consumers to append
> an optional tag to each path. The aggregation of these tagged paths is
> platform specific.
>
> Signed-off-by: Georgi Djakov <georgi.djakov@linaro.org>
> ---
> drivers/interconnect/core.c | 24 +++++++++++++++++++++++-
> drivers/interconnect/qcom/sdm845.c | 2 +-
> include/linux/interconnect-provider.h | 4 ++--
> include/linux/interconnect.h | 5 +++++
> 4 files changed, 31 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/interconnect/core.c b/drivers/interconnect/core.c
> index 871eb4bc4efc..251354bb7fdc 100644
> --- a/drivers/interconnect/core.c
> +++ b/drivers/interconnect/core.c
> @@ -29,6 +29,7 @@ static struct dentry *icc_debugfs_dir;
> * @req_node: entry in list of requests for the particular @node
> * @node: the interconnect node to which this constraint applies
> * @dev: reference to the device that sets the constraints
> + * @tag: path tag (optional)
> * @avg_bw: an integer describing the average bandwidth in kBps
> * @peak_bw: an integer describing the peak bandwidth in kBps
> */
> @@ -36,6 +37,7 @@ struct icc_req {
> struct hlist_node req_node;
> struct icc_node *node;
> struct device *dev;
> + u32 tag;
> u32 avg_bw;
> u32 peak_bw;
> };
> @@ -204,7 +206,7 @@ static int aggregate_requests(struct icc_node *node)
> node->peak_bw = 0;
>
> hlist_for_each_entry(r, &node->req_list, req_node)
> - p->aggregate(node, r->avg_bw, r->peak_bw,
> + p->aggregate(node, r->tag, r->avg_bw, r->peak_bw,
> &node->avg_bw, &node->peak_bw);
>
> return 0;
> @@ -385,6 +387,26 @@ struct icc_path *of_icc_get(struct device *dev, const char *name)
> }
> EXPORT_SYMBOL_GPL(of_icc_get);
>
> +/**
> + * icc_set_tag() - set an optional tag on a path
> + * @path: the path we want to tag
> + * @tag: the tag value
> + *
> + * This function allows consumers to append a tag to the requests associated
> + * with a path, so that a different aggregation could be done based on this tag.
> + */
> +void icc_set_tag(struct icc_path *path, u32 tag)
> +{
> + int i;
> +
> + if (!path)
> + return;
> +
> + for (i = 0; i < path->num_nodes; i++)
> + path->reqs[i].tag = tag;
It's a little unfortunate to have this tag sprayed across all the
request nodes in the path, even though it's really a single value. If
we thought there were likely to be more attributes common to a path
that a provider might want access to, we could add a pointer to the
path in icc_req, then stick the tag in the path. But if the tag ends
up being the only thing worth looking at, then I guess what you have
now is slightly better.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-07-11 17:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-18 9:17 [PATCH v2 0/2] interconnect: Add path tagging support Georgi Djakov
2019-06-18 9:17 ` [PATCH v2 1/2] interconnect: Add support for path tags Georgi Djakov
2019-07-11 17:06 ` Evan Green [this message]
2019-06-18 9:17 ` [PATCH v2 2/2] interconnect: qcom: Add tagging and wake/sleep support for sdm845 Georgi Djakov
2019-07-11 17:06 ` Evan Green
2019-07-15 23:34 ` David Dai
2019-07-16 20:15 ` Evan Green
2019-07-18 17:59 ` David Dai
2019-07-30 22:54 ` Evan Green
2019-07-31 0:37 ` David Dai
2019-07-31 19:06 ` Evan Green
2019-08-02 16:22 ` Georgi Djakov
2019-08-05 15:33 ` [PATCH] interconnect: Add pre_aggregate() callback Georgi Djakov
2019-08-05 16:04 ` Evan Green
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='CAE=gft6=5txOBNEyrzqPEgaZc8ehd4sm5CmDBYOaV+o3-vCNWw@mail.gmail.com' \
--to=evgreen@chromium.org \
--cc=amit.kucheria@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=daidavid1@codeaurora.org \
--cc=dianders@chromium.org \
--cc=georgi.djakov@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=seansw@qti.qualcomm.com \
/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).