From: Ferruh Yigit <ferruh.yigit@intel.com>
To: John Daley <johndale@cisco.com>, <arybchenko@solarflare.com>
Cc: <dev@dpdk.org>, Hyong Youb Kim <hyonkim@cisco.com>
Subject: Re: [PATCH v3] net/enic: support max descriptors allowed by adapter
Date: Fri, 28 Jan 2022 12:58:48 +0000 [thread overview]
Message-ID: <38655efc-1aa9-c66a-0a9a-b70e994ae8ef@intel.com> (raw)
In-Reply-To: <20220127191029.30793-1-johndale@cisco.com>
On 1/27/2022 7:10 PM, John Daley wrote:
> Newer VIC adapters have the max number of supported RX and TX
> descriptors in their configuration. Use these values as the
> maximums.
>
> Signed-off-by: John Daley <johndale@cisco.com>
> Reviewed-by: Hyong Youb Kim <hyonkim@cisco.com>
> ---
> v3: add line just below so 0-day bot applies dependency
> Depends-on: patch-105799 ("net/enic: update VIC firmware API")
Can you please send new version for full set?
next prev parent reply other threads:[~2022-01-28 12:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 3:10 [PATCH 0/3] enic PMD patches John Daley
2022-01-14 3:10 ` [PATCH 1/3] net/enic: add support for eCPRI matching John Daley
2022-01-26 14:00 ` Ferruh Yigit
2022-01-26 14:01 ` Ferruh Yigit
2022-01-27 8:07 ` Thomas Monjalon
2022-01-26 21:48 ` [PATCH v2] " John Daley
2022-01-27 12:15 ` Ferruh Yigit
2022-01-27 18:55 ` [PATCH v3] " John Daley
2022-01-14 3:10 ` [PATCH 2/3] net/enic: update VIC firmware API John Daley
2022-01-14 3:10 ` [PATCH 3/3] net/enic: support max descriptors allowed by adapter John Daley
2022-01-26 14:01 ` Ferruh Yigit
2022-01-26 21:55 ` [PATCH v2] " John Daley
2022-01-27 19:10 ` [PATCH v3] " John Daley
2022-01-28 12:58 ` Ferruh Yigit [this message]
2022-01-28 17:58 ` [PATCH v4 1/3] net/enic: add support for eCPRI matching John Daley
2022-01-28 17:58 ` [PATCH v4 2/3] net/enic: update VIC firmware API John Daley
2022-01-28 17:58 ` [PATCH v4 3/3] net/enic: support max descriptors allowed by adapter John Daley
2022-01-31 11:46 ` [PATCH v4 1/3] net/enic: add support for eCPRI matching 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=38655efc-1aa9-c66a-0a9a-b70e994ae8ef@intel.com \
--to=ferruh.yigit@intel.com \
--cc=arybchenko@solarflare.com \
--cc=dev@dpdk.org \
--cc=hyonkim@cisco.com \
--cc=johndale@cisco.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).