DPDK patches and discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: Wathsala Vithanage <wathsala.vithanage@arm.com>
Cc: Chenbo Xia <chenbox@nvidia.com>,
	Nipun Gupta <nipun.gupta@amd.com>, Gaetan Rivet <grive@u256.net>,
	dev@dpdk.org, nd@arm.com,
	Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>,
	Dhruv Tripathi <dhruv.tripathi@arm.com>
Subject: Re: [RFC v3 1/2] pci: introduce the PCIe TLP Processing Hints API
Date: Tue, 3 Dec 2024 12:54:50 -0800	[thread overview]
Message-ID: <20241203125450.1bc1adb3@hermes.local> (raw)
In-Reply-To: <20241021015246.304431-2-wathsala.vithanage@arm.com>

On Mon, 21 Oct 2024 01:52:45 +0000
Wathsala Vithanage <wathsala.vithanage@arm.com> wrote:

> Extend the PCI driver and the library to extract the Steering Tag (ST)
> for a given Processor/Processor Container and Cache ID pair and validate
> a Processing Hint from a TPH _DSM associated with a root port device.
> The rte_pci_device structure passed into the rte_pci_extract_tph_st()
> function could be a device or a root port. If it's a device, the
> function should trace it back to the root port and use its TPH _DSM to
> extract STs. The implementation of rte_pci_extract_tph_st() is dependent
> on the operating system.
> 
> rte_pci_extract_tph_st() should also be supplied with a
> rte_tph_acpi__dsm_args, and a rte_tph_acpi__dsm_return structures.
> These two structures are defined in the PCI library and comply with the
> TPH _DSM argument and return encoding specified in the PCI firmware ECN
> titled "Revised _DSM for Cache Locality TPH Features.". Use of
> rte_init_tph_acpi__dsm_args() is recommended for initializing the
> rte_tph_acpi__dsm_args struct which is capable of converting lcore ID,
> the cache level into values understood by the ACPI _DSM function.
> rte_tph_acpi__dsm_return struct will be initialized with the values
> returned by the TPH _DSM; it is up to the caller to use these values per
> the device's capabilities.
> 
> Signed-off-by: Wathsala Vithanage <wathsala.vithanage@arm.com>
> Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
> Reviewed-by: Dhruv Tripathi <dhruv.tripathi@arm.com>

While doing review, noticed that patch has minor whitespace issue.

/home/shemminger/DPDK/main/.git/worktrees/stash/rebase-apply/patch:123: new blank line at EOF.
+
warning: 1 line adds whitespace errors.

  reply	other threads:[~2024-12-03 21:14 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-15 22:11 [RFC v2] ethdev: an API for cache stashing hints Wathsala Vithanage
2024-07-17  2:27 ` Stephen Hemminger
2024-07-18 18:48   ` Wathsala Wathawana Vithanage
2024-07-20  3:05   ` Honnappa Nagarahalli
2024-07-17 10:32 ` Konstantin Ananyev
2024-07-22 11:18 ` Ferruh Yigit
2024-07-26 20:01   ` Wathsala Wathawana Vithanage
2024-09-22 21:43     ` Ferruh Yigit
2024-10-04 17:52       ` Stephen Hemminger
2024-10-04 18:46         ` Wathsala Wathawana Vithanage
2024-10-21  1:52 ` [RFC v3 0/2] An API for Stashing Packets into CPU caches Wathsala Vithanage
2024-10-21  1:52   ` [RFC v3 1/2] pci: introduce the PCIe TLP Processing Hints API Wathsala Vithanage
2024-12-03 20:54     ` Stephen Hemminger [this message]
2024-10-21  1:52   ` [RFC v3 2/2] ethdev: introduce the cache stashing hints API Wathsala Vithanage
2024-10-21  7:36     ` Morten Brørup
2024-10-24  5:49     ` Jerin Jacob
2024-10-24  6:59       ` Morten Brørup
2024-10-24 15:12         ` Wathsala Wathawana Vithanage
2024-10-24 15:04       ` Wathsala Wathawana Vithanage
2024-12-03 21:13     ` Stephen Hemminger
2024-12-05 15:40       ` David Marchand
2024-12-05 21:00         ` Stephen Hemminger
2024-10-21  7:35   ` [RFC v3 0/2] An API for Stashing Packets into CPU caches Chenbo Xia
2024-10-21 12:01     ` Wathsala Wathawana Vithanage
2024-10-22  1:12   ` Stephen Hemminger
2024-10-22 18:37     ` Wathsala Wathawana Vithanage
2024-10-22 21:23       ` Stephen Hemminger
2024-10-23 17:59 ` [RFC v2] ethdev: an API for cache stashing hints Mattias Rönnblom
2024-10-23 20:18   ` Stephen Hemminger
2024-10-24 14:59   ` Wathsala Wathawana Vithanage
2024-10-25  7:43   ` Andrew Rybchenko

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=20241203125450.1bc1adb3@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=chenbox@nvidia.com \
    --cc=dev@dpdk.org \
    --cc=dhruv.tripathi@arm.com \
    --cc=grive@u256.net \
    --cc=honnappa.nagarahalli@arm.com \
    --cc=nd@arm.com \
    --cc=nipun.gupta@amd.com \
    --cc=wathsala.vithanage@arm.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).