DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>,
	jerin.jacob@caviumnetworks.com,
	santosh.shukla@caviumnetworks.com, shahafs@mellanox.com
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] net/octeontx: use the new offload APIs
Date: Thu, 5 Apr 2018 14:13:43 +0100	[thread overview]
Message-ID: <4651fa05-ae0a-c703-3a12-537da90f73c1@intel.com> (raw)
In-Reply-To: <20180326110201.8445-1-pbhagavatula@caviumnetworks.com>

On 3/26/2018 12:02 PM, Pavan Nikhilesh wrote:
> Use the new Rx/Tx offload APIs and remove the old style offloads.
> 
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@caviumnetworks.com>
> Acked-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>

<...>

> @@ -630,6 +636,7 @@ octeontx_dev_info(struct rte_eth_dev *dev,
>  	dev_info->default_rxconf = (struct rte_eth_rxconf) {
>  		.rx_free_thresh = 0,
>  		.rx_drop_en = 0,
> +		.offloads = OCTEONTX_RX_OFFLOADS,
>  	};

OCTEONTX_RX_OFFLOADS need to be reported in "rx_offload_capa", currently
"rx_offload_capa" is zero, technically applications are not allowed to set any
Rx offloads.

  reply	other threads:[~2018-04-05 13:13 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-08 19:07 [dpdk-dev] [PATCH] " Pavan Nikhilesh
2018-03-11 18:14 ` santosh
2018-03-21 19:25 ` Ferruh Yigit
2018-03-22  6:26   ` Shahaf Shuler
2018-03-26  7:30   ` Pavan Nikhilesh
2018-03-26 11:02 ` [dpdk-dev] [PATCH v2] " Pavan Nikhilesh
2018-04-05 13:13   ` Ferruh Yigit [this message]
2018-04-05 13:23 ` [dpdk-dev] [PATCH v3] " Pavan Nikhilesh
2018-04-05 13:50   ` 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=4651fa05-ae0a-c703-3a12-537da90f73c1@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=pbhagavatula@caviumnetworks.com \
    --cc=santosh.shukla@caviumnetworks.com \
    --cc=shahafs@mellanox.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).