From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Dai, Wei" <wei.dai@intel.com>, "Wang, Xiao W" <xiao.w.wang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v2 1/2] net/fm10k: convert to new Rx offloads API
Date: Wed, 28 Mar 2018 10:07:39 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E706115317576C@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <20180328080037.16207-2-wei.dai@intel.com>
Hi Daiwei:
> +static uint64_t fm10k_get_rx_queue_offloads_capa(struct rte_eth_dev
> +*dev) {
> + RTE_SET_USED(dev);
> +
> + return (uint64_t)(DEV_RX_OFFLOAD_SCATTER);
> +}
why per queue rx scattered feature here?
My understanding is either we use scattered rx function that enable this feature for all queues or
we use non-scattered rx function that disable this feature for all queues, right?
Regards
Qi
next prev parent reply other threads:[~2018-03-28 10:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-02 14:11 [dpdk-dev] [PATCH] net/fm10k: convert to new Rx/Tx " Wei Dai
2018-03-19 3:54 ` Zhang, Qi Z
2018-03-28 2:56 ` Dai, Wei
2018-03-28 8:00 ` [dpdk-dev] [PATCH v2 0/2] " Wei Dai
2018-03-28 8:00 ` [dpdk-dev] [PATCH v2 1/2] net/fm10k: convert to new Rx " Wei Dai
2018-03-28 10:07 ` Zhang, Qi Z [this message]
2018-03-29 6:08 ` Zhang, Qi Z
2018-03-29 9:29 ` Ananyev, Konstantin
2018-03-29 9:51 ` Zhang, Qi Z
2018-03-29 10:21 ` Ananyev, Konstantin
2018-03-29 10:29 ` Zhang, Qi Z
2018-04-01 12:08 ` Ananyev, Konstantin
2018-04-03 7:10 ` Dai, Wei
2018-04-03 10:48 ` Ananyev, Konstantin
2018-04-04 16:26 ` Ferruh Yigit
2018-03-28 8:00 ` [dpdk-dev] [PATCH v2 2/2] net/fm10k: convert to new Tx " Wei Dai
2018-03-29 6:22 ` [dpdk-dev] [PATCH v2 0/2] net/fm10k: convert to new Rx/Tx " Zhang, Qi Z
2018-03-29 6:57 ` Zhang, Helin
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=039ED4275CED7440929022BC67E706115317576C@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=wei.dai@intel.com \
--cc=xiao.w.wang@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).