DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@amd.com>
To: "Niklas Söderlund" <niklas.soderlund@corigine.com>, dev@dpdk.org
Cc: oss-drivers@corigine.com, Jin Liu <jin.liu@corigine.com>,
	Chaoyong He <chaoyong.he@corigine.com>
Subject: Re: [PATCH] net/nfp: update descriptors logic
Date: Thu, 19 Jan 2023 12:41:06 +0000	[thread overview]
Message-ID: <61409bc0-9254-95c6-e1fe-877cb029e34e@amd.com> (raw)
In-Reply-To: <20221122130948.4100369-1-niklas.soderlund@corigine.com>

On 11/22/2022 1:09 PM, Niklas Söderlund wrote:
> From: Jin Liu <jin.liu@corigine.com>
> 
> The minimum value of TX/RX descriptors for NFP3800 card is not same
> with NFP4000 card, the minimum value of NFP4000 card is 256 while
> NFP3800 card is 512, add the minimum descriptor macro for NFP3800
> card.
> 
> Modify the logic of get descriptor value, assign the value of descriptor
> for the corresponding network card according to its type.
> 
> In TX stage, firmware with NFD3 use one descriptor per packet while
> firmware with NFDk use two descriptors. In order to be consistent
> with the kernel driver, the number of descriptor of firmware with
> NFDk should be divided by 2.
> 
> Signed-off-by: Jin Liu <jin.liu@corigine.com>
> Reviewed-by: Chaoyong He <chaoyong.he@corigine.com>
> Reviewed-by: Niklas Söderlund <niklas.soderlund@corigine.com>
> Signed-off-by: Niklas Söderlund <niklas.soderlund@corigine.com>

Applied to dpdk-next-net/main, thanks.

      reply	other threads:[~2023-01-19 12:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-22 13:09 Niklas Söderlund
2023-01-19 12:41 ` Ferruh Yigit [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=61409bc0-9254-95c6-e1fe-877cb029e34e@amd.com \
    --to=ferruh.yigit@amd.com \
    --cc=chaoyong.he@corigine.com \
    --cc=dev@dpdk.org \
    --cc=jin.liu@corigine.com \
    --cc=niklas.soderlund@corigine.com \
    --cc=oss-drivers@corigine.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).