DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John Miller <john.miller@atomicrules.com>, <dev@dpdk.org>
Cc: <shepard.siegel@atomicrules.com>
Subject: Re: [PATCH v2 1/3] net/ark: add device capabilities record
Date: Mon, 14 Feb 2022 14:00:15 +0000	[thread overview]
Message-ID: <4373c374-ea96-32b1-2954-9aca39e194db@intel.com> (raw)
In-Reply-To: <20220211113935.303366-1-john.miller@atomicrules.com>

On 2/11/2022 11:39 AM, John Miller wrote:
> Add a device capabilities record for supported features.
> Certain variants require that PCIe read-requests be correctly
> throttled. This is called "rqpacing" in Arkville, and has to do
> with credit and flow control on certain Arkville implementations.
> 
> Signed-off-by: John Miller <john.miller@atomicrules.com>
> 
> ---
> v2:
> - Improved code readability and comments.
> ---
>   drivers/net/ark/ark_ethdev.c | 88 +++++++++++++++++++++++++++++-------
>   1 file changed, 71 insertions(+), 17 deletions(-)
> 
> diff --git a/drivers/net/ark/ark_ethdev.c b/drivers/net/ark/ark_ethdev.c
> index b618cba3f0..9f5f375174 100644
> --- a/drivers/net/ark/ark_ethdev.c
> +++ b/drivers/net/ark/ark_ethdev.c
> @@ -85,17 +85,53 @@ static const char * const valid_arguments[] = {
>   	NULL
>   };
>   
> +#define AR_VENDOR_ID 0x1d6c
>   static const struct rte_pci_id pci_id_ark_map[] = {
> -	{RTE_PCI_DEVICE(0x1d6c, 0x100d)},
> -	{RTE_PCI_DEVICE(0x1d6c, 0x100e)},
> -	{RTE_PCI_DEVICE(0x1d6c, 0x100f)},
> -	{RTE_PCI_DEVICE(0x1d6c, 0x1010)},
> -	{RTE_PCI_DEVICE(0x1d6c, 0x1017)},
> -	{RTE_PCI_DEVICE(0x1d6c, 0x1018)},
> -	{RTE_PCI_DEVICE(0x1d6c, 0x1019)},
> +	{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x100d)},
> +	{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x100e)},
> +	{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x100f)},
> +	{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1010)},
> +	{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1017)},
> +	{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1018)},
> +	{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x1019)},
> +	{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101e)},
> +	{RTE_PCI_DEVICE(AR_VENDOR_ID, 0x101f)},

Here two new device support added, can you please separate it
to its own patch?

Also is this new device support deserve driver documentation
or release notes update?

  parent reply	other threads:[~2022-02-14 14:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220119191255.273988-ed.czeck@atomicrules.com>
2022-02-10 14:34 ` John Miller
2022-02-10 14:34   ` [PATCH v2 2/3] net/ark: support arbitrary mbuf size John Miller
2022-02-10 14:34   ` [PATCH v2 3/3] net/ark: support chunk DMA transfers John Miller
2022-02-11 11:39 ` [PATCH v2 1/3] net/ark: add device capabilities record John Miller
2022-02-11 11:39   ` [PATCH v2 2/3] net/ark: support arbitrary mbuf size John Miller
2022-02-11 11:39   ` [PATCH v2 3/3] net/ark: support chunk DMA transfers John Miller
2022-02-14 13:59     ` Ferruh Yigit
2022-02-14 14:00   ` Ferruh Yigit [this message]
2022-02-15 22:19 ` [PATCH v3 1/7] net/ark: add device capabilities record John Miller
2022-02-15 22:19   ` [PATCH v3 2/7] net/ark: add support for new devices John Miller
2022-02-15 22:19   ` [PATCH v3 3/7] net/ark: support arbitrary mbuf size John Miller
2022-02-15 22:19   ` [PATCH v3 4/7] net/ark: packet generator and checker status update John Miller
2022-02-15 22:19   ` [PATCH v3 5/7] net/ark: support chunk DMA transfers John Miller
2022-02-15 22:19   ` [PATCH v3 6/7] net/ark: add memory write barriers in critical code paths John Miller
2022-02-15 22:19   ` [PATCH v3 7/7] net/ark: add performance optimizations John Miller
2022-02-16 10:25   ` [PATCH v3 1/7] net/ark: add device capabilities record Ferruh Yigit

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=4373c374-ea96-32b1-2954-9aca39e194db@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=john.miller@atomicrules.com \
    --cc=shepard.siegel@atomicrules.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).