From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: "Krishna Chaitanya Chundru" <quic_krichai@quicinc.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Daniel Lezcano" <daniel.lezcano@linaro.org>,
"Zhang Rui" <rui.zhang@intel.com>,
linux-pm@vger.kernel.org, linux-pci@vger.kernel.org,
"Bjorn Helgaas" <helgaas@kernel.org>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Rob Herring" <robh@kernel.org>,
"Krzysztof Wilczyński" <kw@linux.com>,
"Lukas Wunner" <lukas@wunner.de>,
"Alexandru Gagniuc" <mr.nuke.me@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Alex Deucher" <alexdeucher@gmail.com>
Subject: Re: [PATCH 00/10] Add PCIe Bandwidth Controller
Date: Tue, 12 Sep 2023 11:08:34 -0700 [thread overview]
Message-ID: <502357b828dd2dd4aa6b5e29969a78dfd206b262.camel@linux.intel.com> (raw)
In-Reply-To: <59c7b5dc2adddf574d0a920e5f7195c418292042.camel@linux.intel.com>
On Tue, 2023-09-12 at 10:45 -0700, srinivas pandruvada wrote:
> On Tue, 2023-09-12 at 15:52 +0300, Ilpo Järvinen wrote:
> > On Mon, 11 Sep 2023, srinivas pandruvada wrote:
> > > On Mon, 2023-09-11 at 18:47 +0300, Ilpo Järvinen wrote:
> > >
> > >
>
> [...]
>
> > > But I don't suggest using such method. This causes confusion and
> > > difficult to change. For example if we increase range of P-state
> > > control, then there is no way to know what is the start point of
> > > T-
> > > states.
> >
> > Yes. I understand it would be confusing.
> >
> > > It is best to create to separate cooling devices for BW and link
> > > width.
> >
> > Okay. If that's the case, then I see no reason to add the Link
> > Width
> > cooling device now as it could do nothing besides reporting the
> > current
> > link width.
> >
> > The only question that then remains is how to take this into
> > account
> > in
> > the naming of the cooling devices, currently PCIe_Port_<pci_name()>
> > is
> > used but perhaps it would be better to change that to
> > PCIe_Port_Link_Speed_... to allow PCI_Port_Link_Width_... to be
> > added
> > later beside it?
> It is better in that way to add BW
sorry, link width controller
> controller later.
>
> Also adding separate cooling device will let thermal configuration,
> choose different method at different thermal thresholds or all
> together.
>
> Thanks,
> Srinivas
>
> >
> > > Also there is a requirement that anything you add to thermal
> > > sysfs,
> > > it
> > > should have some purpose for thermal control. I hope Link width
> > > control
> > > is targeted to similar use case BW control.
> >
> > Ability to control Link Width seems to be part of PCIe 6.0 L0p.
> > AFAICT,
> > the reasons are to lower/control power consumption so it seems to
> > be
> > within scope.
> >
> >
>
prev parent reply other threads:[~2023-09-12 18:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 12:16 [PATCH 00/10] Add PCIe Bandwidth Controller Ilpo Järvinen
2023-08-17 12:16 ` [PATCH 01/10] PCI: Protect Link Control 2 Register with RMW locking Ilpo Järvinen
2023-08-17 12:17 ` [PATCH 02/10] drm/radeon: Use RMW accessors for changing LNKCTL2 Ilpo Järvinen
2023-08-17 12:17 ` [PATCH 03/10] drm/amdgpu: " Ilpo Järvinen
2023-08-17 12:17 ` [PATCH 04/10] drm/IB/hfi1: " Ilpo Järvinen
2023-08-17 12:17 ` [PATCH 05/10] PCI: Store all PCIe Supported Link Speeds Ilpo Järvinen
2023-08-17 12:17 ` [PATCH 06/10] PCI: Cache PCIe device's Supported Speed Vector Ilpo Järvinen
2023-08-17 12:17 ` [PATCH 07/10] PCI/LINK: Re-add BW notification portdrv as PCIe BW controller Ilpo Järvinen
2023-08-17 12:17 ` [PATCH 08/10] PCI/bwctrl: Add "controller" part into PCIe bwctrl Ilpo Järvinen
2023-08-17 12:17 ` [PATCH 09/10] thermal: Add PCIe cooling driver Ilpo Järvinen
2023-08-23 19:47 ` Rafael J. Wysocki
2023-08-17 12:17 ` [PATCH 10/10] selftests/pcie_bwctrl: Create selftests Ilpo Järvinen
2023-09-04 6:26 ` [PATCH 00/10] Add PCIe Bandwidth Controller Krishna Chaitanya Chundru
2023-09-04 11:16 ` Ilpo Järvinen
2023-09-11 13:21 ` Krishna Chaitanya Chundru
2023-09-11 15:47 ` Ilpo Järvinen
2023-09-11 16:14 ` srinivas pandruvada
2023-09-12 12:52 ` Ilpo Järvinen
2023-09-12 17:45 ` srinivas pandruvada
2023-09-12 18:08 ` srinivas pandruvada [this message]
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=502357b828dd2dd4aa6b5e29969a78dfd206b262.camel@linux.intel.com \
--to=srinivas.pandruvada@linux.intel.com \
--cc=alexdeucher@gmail.com \
--cc=daniel.lezcano@linaro.org \
--cc=helgaas@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=lukas@wunner.de \
--cc=mr.nuke.me@gmail.com \
--cc=quic_krichai@quicinc.com \
--cc=rafael@kernel.org \
--cc=robh@kernel.org \
--cc=rui.zhang@intel.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).