DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Mody, Rasesh" <Rasesh.Mody@cavium.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>,
	Andrew Rybchenko <arybchenko@solarflare.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: "Patil, Harish" <Harish.Patil@cavium.com>,
	Dept-Eng DPDK Dev <Dept-EngDPDKDev@cavium.com>
Subject: Re: [dpdk-dev] [PATCH 1/5] net/qede: convert to new Rx/Tx offloads API
Date: Tue, 15 May 2018 19:47:10 +0000	[thread overview]
Message-ID: <MWHPR0701MB367599DDC2D849828E01B3489F930@MWHPR0701MB3675.namprd07.prod.outlook.com> (raw)
In-Reply-To: <69693693-056d-556b-2520-d17824dff34a@intel.com>

> From: Ferruh Yigit [mailto:ferruh.yigit@intel.com]
> Sent: Monday, May 14, 2018 5:53 AM
> 
> On 5/11/2018 10:16 AM, Andrew Rybchenko wrote:
> > On 03/28/2018 03:15 AM, Rasesh Mody wrote:
> >> From: Harish Patil <harish.patil@cavium.com>
> >>
> >> Ethdev RX/TX offloads API has changed since:
> >> commit ce17eddefc20 ("ethdev: introduce Rx queue offloads API")
> >> commit cba7f53b717d ("ethdev: introduce Tx queue offloads API")
> >>
> >> This patch makes use of new offload flags as suggested and fix the
> >> default RX/TX configuration. Also indent the code properly around
> >> those changes.
> >>
> >> Signed-off-by: Harish Patil <harish.patil@cavium.com>
> >> Signed-off-by: Rasesh Mody <rasesh.mody@cavium.com>
> 
> <...>
> 
> >>  				     DEV_TX_OFFLOAD_GENEVE_TNL_TSO);
> >> +	dev_info->tx_queue_offload_capa = dev_info->tx_offload_capa;
> >> +
> >> +	dev_info->default_txconf = (struct rte_eth_txconf) {
> >> +		.txq_flags = DEV_TX_OFFLOAD_MULTI_SEGS,
> >
> > It is incorrect to initialize TxQ flags using Tx offload define.
> 
> Yes it is wrong, thanks for pointing it out. I assume intentions is .offloads
> 
> Rashed, Harish,
> 
> Can you send a fix please?

Fix sent, thanks Andrew.

-Rasesh

> 
> >
> >> +	};
> >> +
> >> +	dev_info->default_rxconf = (struct rte_eth_rxconf) {
> >> +		/* Packets are always dropped if no descriptors are available
> */
> >> +		.rx_drop_en = 1,
> >> +		/* The below RX offloads are always enabled */
> >> +		.offloads = (DEV_RX_OFFLOAD_CRC_STRIP  |
> >> +			     DEV_RX_OFFLOAD_IPV4_CKSUM |
> >> +			     DEV_RX_OFFLOAD_TCP_CKSUM  |
> >> +			     DEV_RX_OFFLOAD_UDP_CKSUM),
> >> +	};
> >>
> >>  	memset(&link, 0, sizeof(struct qed_link_output));
> >>  	qdev->ops->common->get_link(edev, &link);


      reply	other threads:[~2018-05-15 19:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-28  0:15 Rasesh Mody
2018-03-28  0:15 ` [dpdk-dev] [PATCH 2/5] net/qede: enable IPGRE offload support Rasesh Mody
2018-03-28  0:15 ` [dpdk-dev] [PATCH 3/5] net/qede: add devarg to disable NPAR Tx switching Rasesh Mody
2018-03-28  0:15 ` [dpdk-dev] [PATCH 4/5] net/qede: fix device stop to remove primary MAC Rasesh Mody
2018-03-28  0:15 ` [dpdk-dev] [PATCH 5/5] net/qede: fix to prevent overwriting packet type Rasesh Mody
2018-03-30 10:39 ` [dpdk-dev] [PATCH 1/5] net/qede: convert to new Rx/Tx offloads API Ferruh Yigit
2018-05-11  9:16 ` Andrew Rybchenko
2018-05-14 12:53   ` Ferruh Yigit
2018-05-15 19:47     ` Mody, Rasesh [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=MWHPR0701MB367599DDC2D849828E01B3489F930@MWHPR0701MB3675.namprd07.prod.outlook.com \
    --to=rasesh.mody@cavium.com \
    --cc=Dept-EngDPDKDev@cavium.com \
    --cc=Harish.Patil@cavium.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@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).